From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Rick Macklem <rick@snowhite.cis.uoguelph.ca>
Cc: nfs@lists.sourceforge.net, nfsv4@linux-nfs.org, jlayton@redhat.com
Subject: Re: [NFS] [PATCH] NFS: have string-based mount options default to intr mounts
Date: Wed, 25 Jul 2007 16:13:46 -0400 [thread overview]
Message-ID: <1185394426.6585.131.camel@localhost> (raw)
In-Reply-To: <200707252005.QAA25492@snowhite.cis.uoguelph.ca>
On Wed, 2007-07-25 at 16:05 -0400, Rick Macklem wrote:
> > Chuck Lever <chuck.lever@oracle.com> wrote:
> >
> > > I thought "nointr" was the default because it is safest.
> > >
>
> I was actually impressed that "intr" mounts work for NFSv4. I would have
> thought interrupting an RPC that has state related (Open, Lock,...) op(s)
> in it would cause grief later. (NFSERR_BADSEQID or similar)
>
> Do you spin off kernel threads to babysit those outstanding RPCs? rick
Sort of. We run them as independent asynchronous RPC tasks. If the user
interrupts the request, then it is allowed to complete but once it does
then a new RPC call may be sent in order to undo the effects.
Cheers
Trond
prev parent reply other threads:[~2007-07-25 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 20:05 [PATCH] NFS: have string-based mount options default to intr mounts Rick Macklem
2007-07-25 20:13 ` Trond Myklebust [this message]
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=1185394426.6585.131.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=jlayton@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
--cc=rick@snowhite.cis.uoguelph.ca \
/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.