From: Trond Myklebust <trondmy@hammerspace.com>
To: "schumaker.anna@gmail.com" <schumaker.anna@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [GIT PULL] Please pull NFS client updates for 5.1
Date: Mon, 25 Feb 2019 17:51:21 +0000 [thread overview]
Message-ID: <ceb01e5f018a38aa772d23d4ba0ef669b512c101.camel@hammerspace.com> (raw)
In-Reply-To: <486306ab8bb34942b2719b8250950727f382f5ce.camel@gmail.com>
On Fri, 2019-02-22 at 15:54 -0500, Anna Schumaker wrote:
> Hi Trond,
>
> The following changes since commit
> d13937116f1e82bf508a6325111b322c30c85eb9:
>
> Linux 5.0-rc6 (2019-02-10 14:42:20 -0800)
>
> are available in the Git repository at:
>
> git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-rdma-
> for-5.1-1
>
> for you to fetch changes up to
> 2c94b8eca1a26cd46010d6e73a23da5f2e93a19d:
>
> SUNRPC: Use au_rslack when computing reply buffer size (2019-02-14
> 11:58:44
> -0500)
>
> ----------------------------------------------------------------
> New features:
> - Convert rpc auth layer to use xdr_streams
> - Config option to disable insecure enctypes
> - Reduce size of RPC receive buffers
>
> Bugfixes and cleanups:
> - Fix sparse warnings
> - Check inline size before providing a write chunk
> - Reduce the receive doorbell rate
> - Various tracepoint improvements
> ----------------------------------------------------------------
OK pulled, but there were a bunch of conflicts due to the stream record
marker changes. I believe I've fixed them up correctly but please test.
Thanks
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2019-02-25 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 20:54 [GIT PULL] Please pull NFS client updates for 5.1 Anna Schumaker
2019-02-25 17:51 ` 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=ceb01e5f018a38aa772d23d4ba0ef669b512c101.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=linux-nfs@vger.kernel.org \
--cc=schumaker.anna@gmail.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