From: oulijun <oulijun@huawei.com>
To: Bart Van Assche <bvanassche@acm.org>, <dledford@redhat.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>
Cc: linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: 【Question for srpt in kernel-4.14】
Date: Tue, 20 Aug 2019 16:07:49 +0800 [thread overview]
Message-ID: <af84f178-adea-0d1d-9243-837f3942848e@huawei.com> (raw)
In-Reply-To: <e2b80987-a6ff-4693-f15d-5a7c41732401@acm.org>
在 2019/8/20 0:42, Bart Van Assche 写道:
> On 7/23/19 6:35 PM, oulijun wrote:
>> 在 2019/7/23 11:25, oulijun 写道:
>>> 在 2019/7/23 11:13, Bart Van Assche 写道:
>>>> On 7/22/19 6:30 PM, oulijun wrote:
>>>>> 在 2019/7/23 2:07, Bart Van Assche 写道:
>>>>>> On 7/19/19 11:54 PM, oulijun wrote:
>>>>>>> I am targeting a problem about RoCE and SCSI over RDMA from srpt in kernel-4.14. When insmod srpt.ko and insmod hns-roce-hw-v2.ko, it will
>>>>>>> report a warning in srpt_add_one:
>>>>>>> ib_srpt srpt_add_one(hns_0) failed.
>>>>>> How about the following patch?
>>>>>>
>>>>>> diff --git a/drivers/infiniband/ulp/srpt/ib_srpt.c b/drivers/infiniband/ulp/srpt/ib_srpt.c
>>>>>> index 1a039f16d315..e2a4a14763b8 100644
>>>>>> --- a/drivers/infiniband/ulp/srpt/ib_srpt.c
>>>>>> +++ b/drivers/infiniband/ulp/srpt/ib_srpt.c
>>>>>> @@ -3109,7 +3109,8 @@ static void srpt_add_one(struct ib_device *device)
>>>>>> srpt_use_srq(sdev, sdev->port[0].port_attrib.use_srq);
>>>>>>
>>>>>> if (!srpt_service_guid)
>>>>>> - srpt_service_guid = be64_to_cpu(device->node_guid);
>>>>>> + srpt_service_guid = be64_to_cpu(device->node_guid) &
>>>>>> + ~IB_SERVICE_ID_AGN_MASK;
>>>>>>
>>>>>> if (rdma_port_get_link_layer(device, 1) == IB_LINK_LAYER_INFINIBAND)
>>>>>> sdev->cm_id = ib_create_cm_id(device, srpt_cm_handler, sdev);
>>>>>>
>>>>> No, I did not find this patch in the latest kernel-5.3 or others.
>>>> What I meant is: can you try that patch?
> >
>> if we don't add the patch (IB/srpt: Add RDMA/CM support) and only merge your patch, it will not resolve our question.
>>
>> if we add the patch(IB/srpt: Add RDMA/CM support) and merge your patch, it will success.
>
> Did you apply my patch on top of kernel v4.14 or on top of a more recent kernel version?
>
> Thanks,
>
> Bart.
>
No
> .
>
next prev parent reply other threads:[~2019-08-20 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 6:54 【Question for srpt in kernel-4.14】 oulijun
2019-07-22 18:07 ` Bart Van Assche
2019-07-23 1:30 ` oulijun
2019-07-23 3:13 ` Bart Van Assche
2019-07-23 3:25 ` oulijun
2019-07-24 1:35 ` oulijun
2019-08-19 16:42 ` Bart Van Assche
2019-08-20 8:07 ` oulijun [this message]
2019-08-19 16:43 ` Question for srpt in kernel-4.14 Bart Van Assche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af84f178-adea-0d1d-9243-837f3942848e@huawei.com \
--to=oulijun@huawei.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox