From: "J. Bruce Fields" <bfields@fieldses.org>
To: Calum Mackay <calum.mackay@oracle.com>
Cc: "suy.fnst@fujitsu.com" <suy.fnst@fujitsu.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"bfields@redhat.com" <bfields@redhat.com>
Subject: Re: [PATCH] pynfs: courtesy: send RECLAIM_COMPLETE before session2 opening the file
Date: Tue, 15 Jun 2021 11:50:07 -0400 [thread overview]
Message-ID: <20210615155007.GD11877@fieldses.org> (raw)
In-Reply-To: <3f7ee699-bbd6-9025-82b5-40c37cbb6d9c@oracle.com>
On Tue, Jun 15, 2021 at 04:38:15PM +0100, Calum Mackay wrote:
> I wasn't quite sure on the semantics of those calls.
>
> We want what appears to the server to be a new client c2, not a new
> session from an existing client c1. I wasn't sure whether
> new_client_session() would give us that?
Yes, it gets you both a new client and a new session for that client.
It does all the stuff you need to get a new client that you can actually
use for normal operations, so it should be the default unless you need
finer control.
(Also, *eventually*, I want to port all the 4.0 tests to the 4.1 code
and eliminate the separate 4.0/4.1 directories. new_client_session will
then do either exchange_id+create_session+reclaim_complete or
setclientid+setclient_confirm depending on minor version.)
Anyway, so the names are totally unhelpful. Maybe we should reanme
new_client to exchange_id and new_client_session to just new_client.
--b.
next prev parent reply other threads:[~2021-06-15 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 1:01 [PATCH] pynfs: courtesy: send RECLAIM_COMPLETE before session2 opening the file suy.fnst
2021-06-10 11:44 ` Calum Mackay
2021-06-14 20:50 ` Calum Mackay
2021-06-15 14:47 ` J. Bruce Fields
2021-06-15 15:38 ` Calum Mackay
2021-06-15 15:50 ` J. Bruce Fields [this message]
2021-06-15 15:58 ` Calum Mackay
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=20210615155007.GD11877@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=calum.mackay@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=suy.fnst@fujitsu.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