David Chinner wrote:
Why is it necessary to assume that one filesystem block == one buffer?
Is it for atomicity, efficiency, or something else?
By definition, really - each filesystem block has it's own state and
it's own disk mapping and so we need something to carry that
information around....
Well, for block sizes > PAGE_SIZE, you can just duplicate the mapping
information (with an offset-in-block bit field) in each page's struct
page. But I see from your other posts that there are atomicity and
performance reasons as well.
--
error compiling committee.c: too many arguments to function
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
