From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: SQ overflow seen running isert traffic Date: Tue, 18 Oct 2016 10:13:13 -0600 Message-ID: <20161018161313.GC24189@obsidianresearch.com> References: <20160927070157.GA13140@chelsio.com> <672d8b05-5537-d45a-ba3f-cdd5f054a4ab@grimberg.me> <20161017111655.GA21245@chelsio.com> <021001d228a4$6cd6a6c0$4683f440$@opengridcomputing.com> <20161018112801.GA3117@chelsio.com> <005101d2294c$be5bb460$3b131d20$@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <005101d2294c$be5bb460$3b131d20$@opengridcomputing.com> Sender: target-devel-owner@vger.kernel.org To: Steve Wise Cc: 'Sagi Grimberg' , 'Potnuri Bharat Teja' , target-devel@vger.kernel.org, nab@linux-iscsi.org, linux-rdma@vger.kernel.org List-Id: linux-rdma@vger.kernel.org On Tue, Oct 18, 2016 at 09:34:33AM -0500, Steve Wise wrote: > 1) we believe the iSER + RW API correctly sizes the SQ, yet we're seeing SQ > overflows. So the SQ sizing needs more investigation. NFS had this sort of problem - in that case it was because the code was assuming that a RQ completion implied SQ space - that is not legal, only direct completions from SQ WCs can guide available space in the SQ.. Jason