From: Leon Romanovsky <leon@kernel.org>
To: Junxian Huang <huangjunxian6@hisilicon.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next 0/2] RDMA/hns: Support configuring congestion control algorithm with QP granularity
Date: Thu, 8 Feb 2024 10:10:25 +0200 [thread overview]
Message-ID: <20240208081025.GD56027@unreal> (raw)
In-Reply-To: <322ab57d-05d8-72b9-9580-0579b5d8b468@hisilicon.com>
On Wed, Feb 07, 2024 at 04:59:56PM +0800, Junxian Huang wrote:
>
>
> On 2024/2/7 16:33, Leon Romanovsky wrote:
> > On Wed, Feb 07, 2024 at 11:29:08AM +0800, Junxian Huang wrote:
> >> Patch #1 reverts a previous bugfix that was intended to add restriction
> >> to congestion control algorithm for UD but mistakenly introduced other
> >> problem.
> >
> > First patch shouldn't be revert but a fix to "add a restriction that only DCQCN
> > is supported for UD." and second patch should be a new feature.
> >
> > Thanks
> >
>
> OK, but I have two questions here:
>
> 1. Of course we can not only revert but also completely fix the bug in patch #1.
> But since we are adding a new feature that can also fix this bug in patch #2,
> the fix in patch #1 will be immediately removed in patch #2. Is this acceptable?
I would expect that second patch will extend the first one and not remove.
>
> 2. Should I still put these two patches into one patchset in the next version, or
> seperate them into two individual patchset?
Better to separate, as we will take fix faster than new feature.
Thanks
>
> Thanks,
> Junxian
>
> >>
> >> Patch #2 adds support for configuring congestion control algorithm with
> >> QP granularity. The algorithm restriction for UD is added in this patch.
> >>
> >> Junxian Huang (1):
> >> RDMA/hns: Support configuring congestion control algorithm with QP
> >> granularity
> >>
> >> Luoyouming (1):
> >> Revert "RDMA/hns: The UD mode can only be configured with DCQCN"
> >>
> >> drivers/infiniband/hw/hns/hns_roce_device.h | 26 +++++---
> >> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 18 ++----
> >> 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, 118 insertions(+), 20 deletions(-)
> >>
> >> --
> >> 2.30.0
> >>
> >
next prev parent reply other threads:[~2024-02-08 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 3:29 [PATCH for-next 0/2] RDMA/hns: Support configuring congestion control algorithm with QP granularity Junxian Huang
2024-02-07 3:29 ` [PATCH for-next 1/2] Revert "RDMA/hns: The UD mode can only be configured with DCQCN" Junxian Huang
2024-02-07 3:29 ` [PATCH for-next 2/2] RDMA/hns: Support configuring congestion control algorithm with QP granularity Junxian Huang
2024-02-07 8:33 ` [PATCH for-next 0/2] " Leon Romanovsky
2024-02-07 8:59 ` Junxian Huang
2024-02-08 8:10 ` Leon Romanovsky [this message]
2024-02-19 2: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=20240208081025.GD56027@unreal \
--to=leon@kernel.org \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@ziepe.ca \
--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;
as well as URLs for NNTP newsgroup(s).