Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-12-09 Thread Sagi Grimberg
BTW, it's already pushed out, you can look at it now. Looks fine. Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-12-08 Thread Christoph Hellwig
On Thu, Dec 03, 2015 at 05:07:35PM +0200, Sagi Grimberg wrote: > > >Did we ever make progress on this? > > Just up to Doug to pull it in. Doug, any chance to get this into the 4.4 queue? It's annoying having to work around this driver bug in every new ULP. -- To unsubscribe from this list:

Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-12-08 Thread Doug Ledford
On 12/08/2015 01:17 PM, Doug Ledford wrote: > On 12/08/2015 01:13 PM, Sagi Grimberg wrote: >> >>> I've pulled these in. Both of them failed to apply, and the first one >>> was just flat baffling in terms of how Sagi is working from a source >>> base so different than the one in the upstream

Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-12-08 Thread Doug Ledford
On 12/08/2015 12:01 PM, Christoph Hellwig wrote: > On Thu, Dec 03, 2015 at 05:07:35PM +0200, Sagi Grimberg wrote: >> >>> Did we ever make progress on this? >> >> Just up to Doug to pull it in. > > Doug, any chance to get this into the 4.4 queue? It's annoying > having to work around this driver

Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-12-08 Thread Sagi Grimberg
I've pulled these in. Both of them failed to apply, and the first one was just flat baffling in terms of how Sagi is working from a source base so different than the one in the upstream kernel. They should be double checked just to make sure I'm not missing something since they were so far

Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-12-08 Thread Doug Ledford
On 12/08/2015 01:13 PM, Sagi Grimberg wrote: > >> I've pulled these in. Both of them failed to apply, and the first one >> was just flat baffling in terms of how Sagi is working from a source >> base so different than the one in the upstream kernel. They should be >> double checked just to make

Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-12-03 Thread Christoph Hellwig
On Tue, Nov 10, 2015 at 12:36:44PM +0200, Sagi Grimberg wrote: > Any reply on this patchset? Did we ever make progress on this? -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-12-03 Thread Sagi Grimberg
Did we ever make progress on this? Just up to Doug to pull it in. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2 0/2] Handle mlx4 max_sge_rd correctly

2015-11-10 Thread Sagi Grimberg
On 28/10/2015 13:28, Sagi Grimberg wrote: This addresses a specific mlx4 issue where the max_sge_rd is actually smaller than max_sge (rdma reads with max_sge entries completes with error). The second patch removes the explicit work-around from the iser target code. Changes from v1: - Fixed