On Mon, Jun 19, 2006 at 10:47:21AM +0400, Evgeniy Dushistov wrote:
> On Sun, Jun 18, 2006 at 06:50:45PM +0100, Al Viro wrote:
> > * block may be bigger than page. That can cause all sorts of fun
> > problems in interaction with our VM, since allocation can affect more than
> > one page and that has to be taken into account.
>
> In fact this is not a problem. Blocks in terms of linux VFS
> is fragments in terms of UFS.
And?
> And if fragment >4096 we just don't mount such file system.
>
> So we can easily support 32K blocks.
... Which means that we have allocation unit (aka UFS block) covering
several in-core pages. Which means that if you have a file with 8Kb
hole in the beginning, mmap it shared and dirty the first couple of
pages, you will get the situation when parallel writeout on those two
pages will cause trouble. Both times you'll allocate full block (file
is couple of megabytes long, so forget about partial blocks, relocations,
etc.) And both will try to put the reference to what they'd allocated
into the same inode as the first direct block. Do you see the problem?
-
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]
