From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: Kernel fast memory registration API proposal [RFC] Date: Mon, 13 Jul 2015 10:30:15 -0600 Message-ID: <20150713163015.GA23832@obsidianresearch.com> References: <559F8BD1.9080308@dev.mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <559F8BD1.9080308-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sagi Grimberg Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Christoph Hellwig , Steve Wise , Or Gerlitz , Oren Duer , Chuck Lever , Bart Van Assche , Liran Liss , "Hefty, Sean" , Doug Ledford , Tom Talpey List-Id: linux-rdma@vger.kernel.org On Fri, Jul 10, 2015 at 12:09:37PM +0300, Sagi Grimberg wrote: > Given the last discussions on our in-kernel memory registration API I > thought I'd propose another approach to address this. I assume you can put your new indirect registrations under this API without changing the callers? > /* > * Set the SG list in the MR, fail if the sg > * list is not well aligned (caller should handle > * it) or mr does not have enough room to fit the sg. > */ > rc = ib_mr_set_sg(mr, sg, sg_nents); > if (rc) > /* HW does not support - Need to handle it */ I think this call should also do the post. There seems to be nothing the ULP can customize about the post step that needs to be exposed.. and bundling the post allows more flexability to implement different schemes without impacting the ULPs. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html