From: Guangbin Huang <huangguangbin2@huawei.com>
To: <jiri@mellanox.com>, <moshe@mellanox.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <idosch@nvidia.com>
Cc: <edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<huangguangbin2@huawei.com>, <lipeng321@huawei.com>,
<chenhao418@huawei.com>
Subject: [PATCH net-next 0/2] net: hns3: add support setting parameters of congestion control algorithm by devlink param
Date: Fri, 23 Sep 2022 09:38:16 +0800 [thread overview]
Message-ID: <20220923013818.51003-1-huangguangbin2@huawei.com> (raw)
This series adds support setting parameters of congestion control algorithm
by devlink param for HNS3 driver of PF.
There are several parameters need to be set, but the devlink param string
is limited to 32 characters, it is not enough, so expand the string length
to 256.
Hao Chen (2):
devlink: expand __DEVLINK_PARAM_MAX_STRING_VALUE to 256
net: hns3: PF add support setting parameters of congestion control
algorithm by devlink param
.../hns3/hns3_common/hclge_comm_cmd.h | 6 +
.../hisilicon/hns3/hns3pf/hclge_cmd.h | 44 +
.../hisilicon/hns3/hns3pf/hclge_devlink.c | 788 ++++++++++++++++++
.../hisilicon/hns3/hns3pf/hclge_devlink.h | 6 +
.../hisilicon/hns3/hns3pf/hclge_main.c | 122 +++
.../hisilicon/hns3/hns3pf/hclge_main.h | 61 ++
include/net/devlink.h | 2 +-
7 files changed, 1028 insertions(+), 1 deletion(-)
--
2.33.0
next reply other threads:[~2022-09-23 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 1:38 Guangbin Huang [this message]
2022-09-23 1:38 ` [PATCH net-next 1/2] devlink: expand __DEVLINK_PARAM_MAX_STRING_VALUE to 256 Guangbin Huang
2022-09-23 6:13 ` kernel test robot
2022-09-23 1:38 ` [PATCH net-next 2/2] net: hns3: PF add support setting parameters of congestion control algorithm by devlink param Guangbin Huang
2022-09-23 2:23 ` Jakub Kicinski
2022-09-23 2:39 ` huangguangbin (A)
2022-09-23 11:20 ` kernel test robot
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=20220923013818.51003-1-huangguangbin2@huawei.com \
--to=huangguangbin2@huawei.com \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.