From: "Steve Wise" <swise@opengridcomputing.com>
To: "'Chuck Lever'" <chuck.lever@oracle.com>,
<linux-rdma@vger.kernel.org>, <linux-nfs@vger.kernel.org>
Subject: RE: [PATCH v1 0/5] Fix "support large inline thresholds"
Date: Fri, 20 Jan 2017 11:30:37 -0600 [thread overview]
Message-ID: <021301d27342$e9f59fb0$bde0df10$@opengridcomputing.com> (raw)
In-Reply-To: <20170113173023.32692.30661.stgit@manet.1015granger.net>
>
> I've received a number of reports that v4.9 commit 655fec6987be
> ("xprtrdma: Use gathered Send for large inline messages") causes
> NFS/RDMA mounts to fail for devices that have a small max_sge.
>
> This series addresses that problem.
>
> A much smaller fix was provided initially. It worked for devices
> with as small as five send SGEs. However, additional research has
> shown that there is at least one in-tree device that supports only
> three send SGEs.
>
> The current series should enable NFS/RDMA again on those devices.
>
>
> Available in the "nfs-rdma-for-4.10-rc" topic branch of this git repo:
>
> git://git.linux-nfs.org/projects/cel/cel-2.6.git
Hey Chuck,
Tests ok on cxgb4.
Tested-by: Steve Wise <swise@opengridcomputing.com>
next prev parent reply other threads:[~2017-01-20 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 17:42 [PATCH v1 0/5] Fix "support large inline thresholds" Chuck Lever
2017-01-13 17:42 ` [PATCH v1 1/5] xprtrdma: Fix Read chunk padding Chuck Lever
2017-01-13 17:43 ` [PATCH v1 2/5] xprtrdma: Per-connection pad optimization Chuck Lever
2017-01-13 17:43 ` [PATCH v1 3/5] xprtrdma: Disable pad optimization by default Chuck Lever
2017-01-13 17:43 ` [PATCH v1 4/5] xprtrdma: Reduce required number of send SGEs Chuck Lever
2017-01-13 18:01 ` Parav Pandit
2017-01-13 18:30 ` Chuck Lever
2017-01-13 19:14 ` Parav Pandit
2017-01-13 17:43 ` [PATCH v1 5/5] xprtrdma: Shrink send SGEs array Chuck Lever
2017-01-20 17:30 ` Steve Wise [this message]
2017-01-20 18:17 ` [PATCH v1 0/5] Fix "support large inline thresholds" Chuck Lever
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='021301d27342$e9f59fb0$bde0df10$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--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).