From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH rfc 3/3] nvmet-rdma: assign cq completion vector based on the port allowed cpus Date: Thu, 13 Jul 2017 19:24:37 +0200 Message-ID: <20170713172437.GA5236@lst.de> References: <1499007694-7231-1-git-send-email-sagi@grimberg.me> <1499007694-7231-4-git-send-email-sagi@grimberg.me> <20170713155003.GB2577@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Chuck Lever Cc: Christoph Hellwig , Sagi Grimberg , linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, James Smart , Keith Busch , linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On Thu, Jul 13, 2017 at 01:19:00PM -0400, Chuck Lever wrote: > > > On Jul 13, 2017, at 11:50 AM, Christoph Hellwig wrote: > > > > We really shouldn't be doing any of this in NVMe I think. We'll need > > to go back to the cq pool API first. The last version I had was here: > > > > http://git.infradead.org/users/hch/rdma.git/shortlog/refs/heads/rdma-cq > > > > and then do the affinity in common code. > > This seems to address the problem I mentioned to you with properly > estimating send CQ size when using the rdma_rw API. If these are > going to be merged soon, I can drop the new API I proposed here: > > http://git.linux-nfs.org/?p=cel/cel-2.6.git;a=commit;h=2156cb956101da854f64918066710ff4e7affc5b I'd need to find time to get back to it, and I have a few big chunks on my todo list. Any chance you (or someone else interested) could take the series over? -- 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