lkml.org 
[lkml]   [2002]   [Sep]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: invalidate_inode_pages in 2.5.32/3
    Trond Myklebust wrote:
    >
    > >>>>> " " == Andrew Morton <akpm@digeo.com> writes:
    >
    > > Look, idunnoigiveup. Like scsi and USB, NFS is a black hole
    > > where akpms fear to tread. I think I'll sulk until someone
    > > explains why this work has to be performed in the context of a
    > > process which cannot do it.
    >
    > I'd be happy to move that work out of the RPC callbacks if you could
    > point out which other processes actually can do it.

    Well it has to be a new thread, or user processes.

    Would it be possible to mark the inode as "needs invalidation",
    and make user processes check that flag once they have i_sem?

    > The main problem is that the VFS/MM has no way of relabelling pages as
    > being invalid or no longer up to date: I once proposed simply clearing
    > PG_uptodate on those pages which cannot be cleared by
    > invalidate_inode_pages(), but this was not to Linus' taste.

    Yes, clearing PageUptodate without holding the page lock is
    pretty scary.

    Do we really need to invalidate individual pages, or is it real-life
    acceptable to invalidate the whole mapping?

    Doing an NFS-special invalidate function is not a problem, btw - my
    current invalidate_inode_pages() is just 25 lines. It's merely a
    matter of working out what it should do ;)
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:29    [W:0.031 / U:29.868 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site