From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sagi Grimberg Subject: Re: [PATCH RFC 2/3] svcrdma: Use device rdma_read_access_flags Date: Wed, 11 Nov 2015 18:29:15 +0200 Message-ID: <56436CDB.6090305@dev.mellanox.co.il> References: <1447152255-28231-1-git-send-email-sagig@mellanox.com> <1447152255-28231-3-git-send-email-sagig@mellanox.com> <20151110114145.GA2810@infradead.org> <5641D920.5000409@mellanox.com> <20151110120432.GA8230@infradead.org> <20151110182546.GI12667@obsidianresearch.com> <56425AFB.30202@talpey.com> <20151110211716.GA21631@obsidianresearch.com> <564261EF.4000008@talpey.com> <54CF0111-E9C4-4196-BF92-7E134A6A329A@oracle.com> <56430A20.6040600@dev.mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Chuck Lever Cc: Tom Talpey , Jason Gunthorpe , Christoph Hellwig , Linux RDMA Mailing List List-Id: linux-rdma@vger.kernel.org > An alternate explanation is that the provider is not setting > device->max_sge_rd properly. rdma_read_chunks_lcl() seems to > be the only thing in my copy of the kernel tree that relies on > that value. > > I=92ve reproduced the local length errors with CX-2 and CX-3 > Pro, which both set that field to 32. If I artificially > set that field to 30, I don=92t see any issue. > > Is commit 18ebd40773bf correct? See my latest patchset "Handle mlx4 max_sge_rd correctly" (v2). It fixes exactly this. Now you will be able to add your "Tested-by:" tag ;) It on Doug to take it... -- 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