From: Junxian Huang <huangjunxian6@hisilicon.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, <linux-rdma@vger.kernel.org>,
<linuxarm@huawei.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 for-next 2/2] RDMA/hns: Support userspace configuring congestion control algorithm with QP granularity
Date: Mon, 26 Feb 2024 20:57:04 +0800 [thread overview]
Message-ID: <954a1e9b-d0bb-10ea-aaa9-6a958de30537@hisilicon.com> (raw)
In-Reply-To: <20240226080946.GC1842804@unreal>
On 2024/2/26 16:09, Leon Romanovsky wrote:
> On Thu, Feb 22, 2024 at 03:06:20PM +0800, Junxian Huang wrote:
>>
>>
>> On 2024/2/21 23:52, Jason Gunthorpe wrote:
>>> On Thu, Feb 08, 2024 at 11:50:38AM +0800, Junxian Huang wrote:
>>>> Support userspace configuring congestion control algorithm with
>>>> QP granularity. If the algorithm is not specified in userspace,
>>>> use the default one.
>>>>
>>>> Signed-off-by: Junxian Huang <huangjunxian6@hisilicon.com>
>>>> ---
>>>> drivers/infiniband/hw/hns/hns_roce_device.h | 23 +++++--
>>>> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 14 +---
>>>> drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 3 +-
>>>> drivers/infiniband/hw/hns/hns_roce_main.c | 3 +
>>>> drivers/infiniband/hw/hns/hns_roce_qp.c | 71 +++++++++++++++++++++
>>>> include/uapi/rdma/hns-abi.h | 17 +++++
>>>> 6 files changed, 112 insertions(+), 19 deletions(-)
>
> <...>
>
>>>> +
>>>> +enum hns_roce_create_qp_comp_mask {
>>>> + HNS_ROCE_CREATE_QP_MASK_CONGEST_TYPE = 1 << 1,
>>>
>>> Why 1<<1 not 1<<0?
>>
>> This is to keep consistent with our internal ABI, there are some
>> features not upstream yet.
>>
>
> <...>
>
>>>> @@ -114,6 +128,9 @@ struct hns_roce_ib_alloc_ucontext_resp {
>>>> __u32 reserved;
>>>> __u32 config;
>>>> __u32 max_inline_data;
>>>> + __u8 reserved0;
>>>> + __u8 congest_type;
>>>
>>> Why this layout?
>>>> Jason
>>
>> Same as the 1<<1 issue, to keep consistent with our internal ABI.
>
> We are talking about upstream kernel UAPI, there is no internal ABI here.
>
> Please fix it.
>
> Thanks
>
Sure. Will fix it in next version.
Thanks,
Junxian
>>
>> Thanks,
>> Junxian
next prev parent reply other threads:[~2024-02-26 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 3:50 [PATCH v2 for-next 0/2] RDMA/hns: Support " Junxian Huang
2024-02-08 3:50 ` [PATCH v2 for-next 1/2] RDMA/hns: Fix mis-modifying default congestion control algorithm Junxian Huang
2024-02-08 3:50 ` [PATCH v2 for-next 2/2] RDMA/hns: Support userspace configuring congestion control algorithm with QP granularity Junxian Huang
2024-02-21 15:52 ` Jason Gunthorpe
2024-02-22 7:06 ` Junxian Huang
2024-02-26 8:09 ` Leon Romanovsky
2024-02-26 12:57 ` Junxian Huang [this message]
2024-02-26 14:06 ` Jason Gunthorpe
2024-02-27 7:28 ` Junxian Huang
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=954a1e9b-d0bb-10ea-aaa9-6a958de30537@hisilicon.com \
--to=huangjunxian6@hisilicon.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
/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
all inboxes | Powered by JetHome®