Alexander Viro wrote:
* Inodes got a new field: i_bdev. Filesystems should not worry
> about it - just remember to call init_special_inode() when you are
> initializing device/fifo/socket in-core inode (in foo_read_inode() or in
> foo_mknod(); all filesystems in the tree are doing it now).
When you say inodes, do you mean in ram or on disk or both?
Adding fields to the already bloated inode structure is (generally) not a good
thing. It makes use of files for small objects less effective, which affects the
applicability of filesystems to new applications like web search engine indexes.
Why do you need it, I am curious?
I do not mean to be discouraging of someone cleaning up old datastructures and
making them better....
I just want to understand the change. Is the intent to get rid of i_rdev and
replace it with i_bdev?
Hans
-- Get Linux (http://www.kernel.org) plus ReiserFS (http://devlinux.org/namesys). If you sell an OS or internet appliance, buy a port of ReiserFS! If you need customizations and industrial grade support, we sell them.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:15 EST