> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Devesh Sharma
> Sent: Friday, March 27, 2015 11:13 AM
> To: Anna Schumaker; Chuck Lever; linux-rdma@vger.kernel.org; linux-
> n...@vger.kernel.org
> Subject: RE: [PATCH v2
Hi Chuck,
I have validated these set of patches with ocrdma device, iozone passes with
these.
-Regards
Devesh
> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Anna Schumaker
> Sent: Friday, March 27, 2015 12:10 AM
>
On Thu, Mar 26, 2015 at 05:58:20PM +0100, Michael Wang wrote:
> The questions is just wondering how the transition method could be, but
> if we have to do the changes for vendor, that sounds like a tough job...
I would see changing how the information is represented in the struct
as a follow on i
Hey Chuck,
I didn't see anything that needs to be fixed up in these patches. Are they
ready for me?
Anna
On 03/24/2015 04:30 PM, Chuck Lever wrote:
> This is a series of client-side patches for NFS/RDMA. In preparation
> for increasing the transport credit limit and maximum rsize/wsize,
> I've
On Mar 26, 2015, at 1:39 PM, Anna Schumaker wrote:
> Hey Chuck,
>
> I didn't see anything that needs to be fixed up in these patches. Are they
> ready for me?
Thanks for the review. IMO we can go one of two routes:
- Wait for HCA vendors to test this latest version of the series, or
- Me
On 03/26/2015 05:27 PM, Doug Ledford wrote:
> On Thu, 2015-03-26 at 17:04 +0100, Michael Wang wrote:
>> [snip]
>>
>> Few more questions here is:
>> 1. when to setup? (maybe inside ib_register_device() before doing
>> client->add() callback?)
> I don't think "we" can set it up here. The driver's h
On Thu, 2015-03-26 at 17:04 +0100, Michael Wang wrote:
> Hi, Doug
>
> Thanks for the excellent comments :-)
>
> On 03/26/2015 03:09 PM, Doug Ledford wrote:
> > On Wed, 2015-03-25 at 16:09 +0100, Michael Wang wrote:
> >> [snip]
> >>
> > [snip]
> >
> > So, I would suggest that we fix things up thus
Hi everyone.
I have been trying to get inline-receive functionality to work on
Connect-IB cards. However, it seems like libmlx5 (from Mellanox OFED
2.4) does not support inline-receive. libmlx4 seems to support it, but
I believe libmlx4 is not compatible with Connect-IB cards. Further,
the Mellano
Hi, Doug
Thanks for the excellent comments :-)
On 03/26/2015 03:09 PM, Doug Ledford wrote:
> On Wed, 2015-03-25 at 16:09 +0100, Michael Wang wrote:
>> [snip]
>>
> [snip]
>
> So, I would suggest that we fix things up thusly:
>
> enum transport {
> TRANSPORT_IB=1,
> TRANSPORT_IWARP=2,
>
On Wed, 2015-03-25 at 16:09 +0100, Michael Wang wrote:
> My sincerely apologies for the corrupted mails, and thanks for Dan's kindly
> remind :-)
>
> There are too many lengthy code to check the transport type of IB device,
> or the link layer type of it's port, this patch set try to use some help
Hi Matan/Moni,
Could either of you please respond to both of Bart's
queries?
Thanks
Somnath
> -Original Message-
> From: Bart Van Assche [mailto:bart.vanass...@sandisk.com]
> Sent: Thursday, March 26, 2015 5:13 AM
> To: Somnath Kotur; rol...@kernel.org
> Cc: linux-rdm
11 matches
Mail list logo
