From: Tom Talpey <tom@talpey.com>
To: Devesh Sharma <devesh.sharma@avagotech.com>,
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 09/12] xprtrdma: Prepare rpcrdma_ep_post() for RDMA_NOMSG calls
Date: Fri, 10 Jul 2015 08:58:34 -0400 [thread overview]
Message-ID: <559FC17A.7060502@talpey.com> (raw)
In-Reply-To: <CANjDDBh38PrxGgWGuKYCYcbjqY9ELrpkGqaRZ_ueKfD7FEQP8g@mail.gmail.com>
On 7/10/2015 7:29 AM, Devesh Sharma wrote:
> we need to honor the max limits of device by checking
> dev_attr.max_sge? a vendor may not support 4 sges.
iWARP requires a minimum of 4 send SGEs (draft-hilland-verbs 8.1.3.2)
An RI MUST support at least four Scatter/Gather Elements per
Scatter/Gather List when the Scatter/Gather List refers to the Data
Source of a Send Operation Type or the Data Sink of a Receive
Operation. An RI is NOT REQUIRED to support more than one
Scatter/Gather Element per Scatter/Gather List when the
Scatter/Gather List refers to the Data Source of an RDMA Write.
I'm not certain if IB and RoCE state a similar minimum requirement,
but it seems a very bad idea to have fewer.
WARNING: multiple messages have this Message-ID (diff)
From: Tom Talpey <tom-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org>
To: Devesh Sharma
<devesh.sharma-1wcpHE2jlwO1Z/+hSey0Gg@public.gmane.org>,
Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux NFS Mailing List
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v1 09/12] xprtrdma: Prepare rpcrdma_ep_post() for RDMA_NOMSG calls
Date: Fri, 10 Jul 2015 08:58:34 -0400 [thread overview]
Message-ID: <559FC17A.7060502@talpey.com> (raw)
In-Reply-To: <CANjDDBh38PrxGgWGuKYCYcbjqY9ELrpkGqaRZ_ueKfD7FEQP8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 7/10/2015 7:29 AM, Devesh Sharma wrote:
> we need to honor the max limits of device by checking
> dev_attr.max_sge? a vendor may not support 4 sges.
iWARP requires a minimum of 4 send SGEs (draft-hilland-verbs 8.1.3.2)
An RI MUST support at least four Scatter/Gather Elements per
Scatter/Gather List when the Scatter/Gather List refers to the Data
Source of a Send Operation Type or the Data Sink of a Receive
Operation. An RI is NOT REQUIRED to support more than one
Scatter/Gather Element per Scatter/Gather List when the
Scatter/Gather List refers to the Data Source of an RDMA Write.
I'm not certain if IB and RoCE state a similar minimum requirement,
but it seems a very bad idea to have fewer.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-10 13:05 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 20:41 [PATCH v1 00/12] NFS/RDMA client side for Linux 4.3 Chuck Lever
2015-07-09 20:41 ` Chuck Lever
2015-07-09 20:41 ` [PATCH v1 01/12] xprtrdma: Make xprt_setup_rdma() agnostic to family of server address Chuck Lever
2015-07-09 20:41 ` Chuck Lever
2015-07-09 20:41 ` [PATCH v1 02/12] xprtrdma: Raise maximum payload size to one megabyte Chuck Lever
2015-07-09 20:41 ` Chuck Lever
2015-07-10 10:25 ` Devesh Sharma
2015-07-10 10:25 ` Devesh Sharma
2015-07-10 19:21 ` Anna Schumaker
2015-07-10 19:21 ` Anna Schumaker
2015-07-10 19:33 ` Chuck Lever
2015-07-10 19:33 ` Chuck Lever
2015-07-10 19:41 ` Anna Schumaker
2015-07-10 19:41 ` Anna Schumaker
2015-07-12 14:31 ` Sagi Grimberg
2015-07-12 14:31 ` Sagi Grimberg
2015-07-09 20:42 ` [PATCH v1 03/12] xprtrdma: Increase default credit limit Chuck Lever
2015-07-09 20:42 ` Chuck Lever
2015-07-10 10:45 ` Devesh Sharma
2015-07-10 10:45 ` Devesh Sharma
2015-07-10 14:33 ` Chuck Lever
2015-07-10 14:33 ` Chuck Lever
2015-07-10 14:47 ` Devesh Sharma
2015-07-10 14:47 ` Devesh Sharma
2015-07-12 14:31 ` Sagi Grimberg
2015-07-12 14:31 ` Sagi Grimberg
2015-07-09 20:42 ` [PATCH v1 04/12] xprtrdma: Remove last ib_reg_phys_mr() call site Chuck Lever
2015-07-09 20:42 ` Chuck Lever
2015-07-10 10:52 ` Devesh Sharma
2015-07-10 10:52 ` Devesh Sharma
2015-07-11 10:34 ` Christoph Hellwig
2015-07-11 10:34 ` Christoph Hellwig
2015-07-11 18:50 ` Chuck Lever
2015-07-11 18:50 ` Chuck Lever
2015-07-12 7:58 ` Christoph Hellwig
2015-07-12 7:58 ` Christoph Hellwig
2015-07-12 14:31 ` Sagi Grimberg
2015-07-12 14:31 ` Sagi Grimberg
2015-07-09 20:42 ` [PATCH v1 05/12] xprtrdma: Account for RPC/RDMA header size when deciding to inline Chuck Lever
2015-07-09 20:42 ` Chuck Lever
2015-07-10 10:55 ` Devesh Sharma
2015-07-10 10:55 ` Devesh Sharma
2015-07-10 20:08 ` Anna Schumaker
2015-07-10 20:08 ` Anna Schumaker
2015-07-10 20:28 ` Chuck Lever
2015-07-10 20:28 ` Chuck Lever
2015-07-12 14:37 ` Sagi Grimberg
2015-07-12 14:37 ` Sagi Grimberg
2015-07-12 17:52 ` Chuck Lever
2015-07-12 17:52 ` Chuck Lever
2015-07-09 20:42 ` [PATCH v1 06/12] xprtrdma: Always provide a write list when sending NFS READ Chuck Lever
2015-07-09 20:42 ` Chuck Lever
2015-07-10 11:08 ` Devesh Sharma
2015-07-10 11:08 ` Devesh Sharma
2015-07-12 14:42 ` Sagi Grimberg
2015-07-12 14:42 ` Sagi Grimberg
2015-07-09 20:42 ` [PATCH v1 07/12] xprtrdma: Don't provide a reply chunk when expecting a short reply Chuck Lever
2015-07-09 20:42 ` Chuck Lever
2015-07-12 14:58 ` Sagi Grimberg
2015-07-12 14:58 ` Sagi Grimberg
2015-07-12 18:38 ` Chuck Lever
2015-07-12 18:38 ` Chuck Lever
2015-07-14 9:54 ` Sagi Grimberg
2015-07-14 9:54 ` Sagi Grimberg
2015-07-09 20:42 ` [PATCH v1 08/12] xprtrdma: Fix XDR tail buffer marshalling Chuck Lever
2015-07-09 20:42 ` Chuck Lever
2015-07-09 20:43 ` [PATCH v1 09/12] xprtrdma: Prepare rpcrdma_ep_post() for RDMA_NOMSG calls Chuck Lever
2015-07-09 20:43 ` Chuck Lever
2015-07-10 11:29 ` Devesh Sharma
2015-07-10 11:29 ` Devesh Sharma
2015-07-10 12:58 ` Tom Talpey [this message]
2015-07-10 12:58 ` Tom Talpey
2015-07-10 14:11 ` Devesh Sharma
2015-07-10 14:11 ` Devesh Sharma
2015-07-10 14:53 ` Chuck Lever
2015-07-10 14:53 ` Chuck Lever
2015-07-10 22:44 ` Jason Gunthorpe
2015-07-10 22:44 ` Jason Gunthorpe
2015-07-10 20:43 ` Anna Schumaker
2015-07-10 20:43 ` Anna Schumaker
2015-07-10 20:52 ` Chuck Lever
2015-07-10 20:52 ` Chuck Lever
2015-07-09 20:43 ` [PATCH v1 10/12] xprtrdma: Fix large NFS SYMLINK calls Chuck Lever
2015-07-09 20:43 ` Chuck Lever
2015-07-14 16:01 ` Anna Schumaker
2015-07-14 16:01 ` Anna Schumaker
2015-07-14 19:09 ` Chuck Lever
2015-07-14 19:09 ` Chuck Lever
2015-07-09 20:43 ` [PATCH v1 11/12] xprtrdma: Clean up xprt_rdma_print_stats() Chuck Lever
2015-07-09 20:43 ` Chuck Lever
2015-07-09 20:43 ` [PATCH v1 12/12] xprtrdma: Count RDMA_NOMSG type calls Chuck Lever
2015-07-09 20:43 ` 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=559FC17A.7060502@talpey.com \
--to=tom@talpey.com \
--cc=chuck.lever@oracle.com \
--cc=devesh.sharma@avagotech.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 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.