Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Scott Mayhew <smayhew@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Add notifier blocks to close transport sockets when an ip address is deleted
Date: Fri, 18 Dec 2015 09:54:13 -0500	[thread overview]
Message-ID: <20151218145413.GB25074@fieldses.org> (raw)
In-Reply-To: <20151218135541.GO4405@tonberry.usersys.redhat.com>

On Fri, Dec 18, 2015 at 08:55:41AM -0500, Scott Mayhew wrote:
> On Thu, 17 Dec 2015, J. Bruce Fields wrote:
> 
> > On Fri, Dec 11, 2015 at 04:45:57PM -0500, Scott Mayhew wrote:
> > > For this to be effective, the clients still need to mount with a lower timeout,
> > > but it doesn't need to be as aggressive as 1/10 of a second.
> > 
> > That's just to prevent a file operation hanging too long in the case
> > that nfsd or ip shutdown prevents the client getting a reply?
> 
> That statement was based on early testing actually.  I went on to test 
> with timeouts of 3, 10, 30, and 60 seconds, and it no longer appeared to
> make a difference.  I just forgot to remove that from my final cover
> letter.

OK.  Though the window to hit the lost-reply case might be very small,
I'm not sure.

--b.

      reply	other threads:[~2015-12-18 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 21:45 [PATCH 0/3] Add notifier blocks to close transport sockets when an ip address is deleted Scott Mayhew
2015-12-11 21:45 ` [PATCH 1/3] sunrpc: Add a function to close temporary transports immediately Scott Mayhew
2015-12-11 21:45 ` [PATCH 2/3] nfsd: Register callbacks on the inetaddr_chain and inet6addr_chain Scott Mayhew
2015-12-11 21:46 ` [PATCH 3/3] lockd: " Scott Mayhew
2015-12-17 19:57 ` [PATCH 0/3] Add notifier blocks to close transport sockets when an ip address is deleted J. Bruce Fields
2015-12-17 22:17   ` J. Bruce Fields
2015-12-18 13:57     ` Scott Mayhew
2015-12-18 13:55   ` Scott Mayhew
2015-12-18 14:54     ` J. Bruce Fields [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=20151218145413.GB25074@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smayhew@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox