[lkml]   [2002]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: invalidate_inode_pages in 2.5.32/3
Trond Myklebust wrote:
> >>>>> " " == Chuck Lever <> writes:
> > rpciod must never call a function that sleeps. if this
> > happens, the whole NFS client stops working until the function
> > wakes up again. this is not really bogus -- it is similar to
> > restrictions placed on socket callbacks.
> I'm in France at the moment, and am therefore not really able to
> follow up on this thread for the moment. I'll try to clarify the above
> though:
> 2 reasons why rpciod cannot block:
> 1) Doing so will slow down I/O for *all* NFS users.
> 2) There's a minefield of possible deadlock situations: waiting on a
> locked page is the main no-no since rpciod itself is the process
> that needs to complete the read I/O and unlock the page.

Yes. Both of these would indicate that rpciod is the wrong process
to be performing the invalidation.

Is it not possible to co-opt a user process to perform the
invalidation? Just

inode->is_kaput = 1;

in rpciod?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.245 / U:0.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site