From: Vallish Vaidyeshwara <vallish@amazon.com>
To: "bfields@fieldses.org" <bfields@fieldses.org>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"jsstraus@amazon.com" <jsstraus@amazon.com>
Subject: Re: [PATCH 2/2] SUNRPC: Reconnect with new port on server initiated connection termination
Date: Thu, 10 May 2018 21:15:46 +0000 [thread overview]
Message-ID: <20180510211546.GB50901@amazon.com> (raw)
In-Reply-To: <20180510173728.GA3736@fieldses.org>
On Thu, May 10, 2018 at 01:37:28PM -0400, bfields@fieldses.org wrote:
> On Thu, May 10, 2018 at 04:22:02PM +0000, Vallish Vaidyeshwara wrote:
> > If the server has closed a connection, then no DRC state remains on the server
> > we want to use.
>
> That's not a rule, as far as I know. Certainly the Linux server doesn't
> destroy DRC state on closing a connection. (Should it? I'm not sure
> that's a good idea.)
>
> --b.
>
Thanks for the clarification and I agree patch 2 should not be applied.
prev parent reply other threads:[~2018-05-10 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 6:12 [PATCH 0/2] SUNRPC: Clean up port reuse behavior on reconnects Vallish Vaidyeshwara
2018-05-10 6:12 ` [PATCH 1/2] SUNRPC: Need to reuse non-reserved port for reconnect Vallish Vaidyeshwara
2018-05-10 21:18 ` Vallish Vaidyeshwara
2018-05-10 6:12 ` [PATCH 2/2] SUNRPC: Reconnect with new port on server initiated connection termination Vallish Vaidyeshwara
2018-05-10 15:25 ` Trond Myklebust
2018-05-10 16:22 ` Vallish Vaidyeshwara
2018-05-10 17:26 ` Trond Myklebust
2018-05-10 21:12 ` Vallish Vaidyeshwara
2018-05-10 17:37 ` bfields
2018-05-10 21:15 ` Vallish Vaidyeshwara [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=20180510211546.GB50901@amazon.com \
--to=vallish@amazon.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=jsstraus@amazon.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.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 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.