From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [PATCH v1 09/12] xprtrdma: Prepare rpcrdma_ep_post() for RDMA_NOMSG calls Date: Fri, 10 Jul 2015 16:44:02 -0600 Message-ID: <20150710224402.GA8342@obsidianresearch.com> References: <20150709203242.26247.4848.stgit@manet.1015granger.net> <20150709204305.26247.39173.stgit@manet.1015granger.net> <559FC17A.7060502@talpey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sagi Grimberg Cc: Devesh Sharma , Tom Talpey , linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linux NFS Mailing List , Chuck Lever List-Id: linux-rdma@vger.kernel.org On Fri, Jul 10, 2015 at 10:53:40AM -0400, Chuck Lever wrote: > It is certainly possible to examine the device=E2=80=99s max_sge fiel= d > in rpcrdma_ep_create() and fail transport creation if the > device=E2=80=99s max_sge is less than RPC_MAX_IOVS. I just want to draw Sagi's attention to this problem, when considering my thoughts on an alternate API for posting. This thread is about NFS needing 4 sges for a (rare?) message type. The API direction I suggested addresses this kind of issue as well, because under the covers the driver/core can spin up a temporary MR for this case and thus support an infinite s/g list for all posts. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" i= n the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html