lkml.org 
[lkml]   [2002]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: invalidate_inode_pages in 2.5.32/3
Daniel Phillips wrote:
>
> ...
> > Is it not possible to co-opt a user process to perform the
> > invalidation? Just
> >
> > inode->is_kaput = 1;
> >
> > in rpciod?
>
> There must be a way. The key thing the VM needs to provide, and doesn't
> now, is a function callable by the rpciod that will report to the caller
> whether it was able to complete the invalidation without blocking. (I
> think I'm just rephrasing someone's earlier suggestion here.)
>
> I'm now thinking in general terms about how to concoct a mechanism
> that lets rpciod retry the invalidation later, for all those that turn
> out to be blocking. For example, rpciod could just keep a list of
> all pending invalidates and retry each inode on the list every time
> it has nothing to do. This is crude and n-squarish, but it would
> work. Maybe it's efficient enough for the time being. At least it's
> correct, which would be a step forward.

rpciod is the wrong process to be performing this operation. I'd suggest
the userspace process which wants to read the directory be used for this.

> Did you have some specific mechanism in mind?
>

Testing mapping->nrpages will tell you if the invalidation was successful.
-
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:28    [W:0.114 / U:0.048 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site