Hi,

On Fri, Jul 06, 2007 at 05:57:49PM +0200, Jorn Engel wrote:

On Fri, 6 July 2007 09:52:14 -0400, Chris Mason wrote:

quoted

On Fri, 6 Jul 2007 23:42:01 +1000 David Chinner [off-list ref] wrote:

quoted

Hmmm - I guess you could use it for writeback ordering. I hadn't
really thought about that. Doesn't seem a particularly efficient way
of doing it, though. Why not just use multiple address spaces for
this? i.e. one per level and flush in ascending order.

Interesting idea.  Is it possible to attach several address spaces to an
inode?  That would cure some headaches.

GFS2 already uses something like this, in fact by having a second inode
to contain the second address space. Thats a bit of a hack but we can't
put the second address space into the inode since that causes problems
during writeback of inodes. So our perferred solution would be to put
the second address space into the glock structure, but we can't do that
until some of the VFS/VM routines can cope with mapping->host not being
an inode.

So that would certainly be an issue that I'd like to discuss to see
what can be worked out in that area,

Steve.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>