From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-rdma@vger.kernel.org,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v1 0/4] NFS/RDMA server patches for v4.19
Date: Wed, 1 Aug 2018 11:20:38 -0400 [thread overview]
Message-ID: <20180801152038.GB18338@fieldses.org> (raw)
In-Reply-To: <A73AEC28-2A67-4EFB-8C42-0B0842F4DF4D@oracle.com>
On Wed, Aug 01, 2018 at 11:14:14AM -0400, Chuck Lever wrote:
> > On Aug 1, 2018, at 10:36 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > But I'd rather not invest a lot of time trying to make NFSv2/v3 better,
> > the priority for older protocols is just to avoid regressions.
>
> Fair 'nuf.
>
> I'm not clear where NFSv4.0 fits here. I realize most of us would
> consider NFSv4.0 to be a "legacy protocol". Does the Linux server
> utilize the DRC for NFSv4.0 ?
If I remember correctly, it uses the DRC and decides whether to cache
particular compounds based on the mix of operation numbers making up the
compound. (I wrote that code but haven't looked at it recently.)--b.
prev parent reply other threads:[~2018-08-01 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 15:18 [PATCH v1 0/4] NFS/RDMA server patches for v4.19 Chuck Lever
2018-07-27 15:18 ` [PATCH v1 1/4] svcrdma: Avoid releasing a page in svc_xprt_release() Chuck Lever
2018-07-27 15:18 ` [PATCH v1 2/4] svcrdma: Clean up Read chunk path Chuck Lever
2018-07-27 15:19 ` [PATCH v1 3/4] NFSD: Refactor the generic write vector fill helper Chuck Lever
2018-11-15 16:32 ` J. Bruce Fields
2018-11-16 0:19 ` Chuck Lever
2018-11-19 19:54 ` Bruce Fields
2018-11-19 19:58 ` Chuck Lever
2018-11-19 19:59 ` Bruce Fields
2018-07-27 15:19 ` [PATCH v1 4/4] NFSD: Handle full-length symlinks Chuck Lever
2018-08-01 14:14 ` J. Bruce Fields
2018-08-01 14:16 ` Chuck Lever
2018-08-01 14:36 ` [PATCH v1 0/4] NFS/RDMA server patches for v4.19 J. Bruce Fields
2018-08-01 15:14 ` Chuck Lever
2018-08-01 15:20 ` 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=20180801152038.GB18338@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).