From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Peter Åstrand" <astrand@lysator.liu.se>
Cc: nfs@lists.sourceforge.net
Subject: Re: Re: NFS retry on disconnection
Date: 14 May 2002 10:16:59 +0200 [thread overview]
Message-ID: <shssn4vf8jo.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0205140833140.20950-100000@sofie.lambo.student.liu.se>
>>>>> " " == astrand <Peter> writes:
> One thing that keeps annoying me is that "intr" only allows
> interrupting the file operation when a major timeout happens. I
Nope. Major, minor, it all goes through the same code and both can be
interrupted. What can happen, though, is that one process could
actually be waiting on another process.
If, say, they are both waiting to read data from the same page, then
only one process actually does the RPC call. The VFS/MM layers will
put the other process to sleep in the global function 'lock_page()'.
That unfortunately means that it cannot interrupt, since 'lock_page()'
does not do interruptible sleeps.
Cheers,
Trond
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-05-14 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 6:37 Re: NFS retry on disconnection Peter Åstrand
2002-05-14 8:16 ` Trond Myklebust [this message]
2002-05-14 8:38 ` Peter Astrand
2002-05-14 9:31 ` Trond Myklebust
2002-05-14 22:52 ` Ion Badulescu
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 16:17 Bryan Henderson
2002-05-13 19:53 ` Ion Badulescu
2002-05-13 21:04 ` Greg Lindahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=shssn4vf8jo.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=astrand@lysator.liu.se \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.