From: Leon Romanovsky <leon@kernel.org>
To: Yufeng Mo <moyufeng@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
shenjian15@huawei.com, lipeng321@huawei.com,
yisen.zhuang@huawei.com, linyunsheng@huawei.com,
zhangjiaran@huawei.com, huangguangbin2@huawei.com,
chenhao288@hisilicon.com, salil.mehta@huawei.com,
linuxarm@huawei.com, linuxarm@openeuler.org
Subject: Re: [PATCH RFC] net: hns3: add a module parameter wq_unbound
Date: Tue, 20 Jul 2021 12:01:06 +0300 [thread overview]
Message-ID: <YPaQ0qW+uIToEM6c@unreal> (raw)
In-Reply-To: <1626770097-56989-1-git-send-email-moyufeng@huawei.com>
On Tue, Jul 20, 2021 at 04:34:57PM +0800, Yufeng Mo wrote:
> To meet the requirements of different scenarios, the WQ_UNBOUND
> flag of the workqueue is transferred as a module parameter. Users
> can flexibly configure the usage mode as required.
>
> Signed-off-by: Yufeng Mo <moyufeng@huawei.com>
> ---
> drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 10 +++++++++-
> drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c | 10 +++++++++-
> 2 files changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
> index dd3354a..9816592 100644
> --- a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c
> @@ -76,6 +76,10 @@ static struct hnae3_ae_algo ae_algo;
>
> static struct workqueue_struct *hclge_wq;
>
> +static unsigned int wq_unbound;
> +module_param(wq_unbound, uint, 0400);
> +MODULE_PARM_DESC(wq_unbound, "Specifies WQ_UNBOUND flag for the workqueue, non-zero value takes effect");
Nice, but no. We don't like module parameters for such a basic thing.
Somehow all other NIC drivers in the world works without it and hns3
will success too.
Thanks
> +
> static const struct pci_device_id ae_algo_pci_tbl[] = {
> {PCI_VDEVICE(HUAWEI, HNAE3_DEV_ID_GE), 0},
> {PCI_VDEVICE(HUAWEI, HNAE3_DEV_ID_25GE), 0},
> @@ -12936,7 +12940,11 @@ static int hclge_init(void)
> {
> pr_info("%s is initializing\n", HCLGE_NAME);
>
> - hclge_wq = alloc_workqueue("%s", 0, 0, HCLGE_NAME);
> + if (wq_unbound)
> + hclge_wq = alloc_workqueue("%s", WQ_UNBOUND, 0, HCLGE_NAME);
> + else
> + hclge_wq = alloc_workqueue("%s", 0, 0, HCLGE_NAME);
> +
> if (!hclge_wq) {
> pr_err("%s: failed to create workqueue\n", HCLGE_NAME);
> return -ENOMEM;
> diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c b/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c
> index 52eaf82..85f6772 100644
> --- a/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c
> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c
> @@ -21,6 +21,10 @@ static struct hnae3_ae_algo ae_algovf;
>
> static struct workqueue_struct *hclgevf_wq;
>
> +static unsigned int wq_unbound;
> +module_param(wq_unbound, uint, 0400);
> +MODULE_PARM_DESC(wq_unbound, "Specifies WQ_UNBOUND flag for the workqueue, non-zero value takes effect");
> +
> static const struct pci_device_id ae_algovf_pci_tbl[] = {
> {PCI_VDEVICE(HUAWEI, HNAE3_DEV_ID_VF), 0},
> {PCI_VDEVICE(HUAWEI, HNAE3_DEV_ID_RDMA_DCB_PFC_VF),
> @@ -3855,7 +3859,11 @@ static int hclgevf_init(void)
> {
> pr_info("%s is initializing\n", HCLGEVF_NAME);
>
> - hclgevf_wq = alloc_workqueue("%s", 0, 0, HCLGEVF_NAME);
> + if (wq_unbound)
> + hclgevf_wq = alloc_workqueue("%s", WQ_UNBOUND, 0, HCLGEVF_NAME);
> + else
> + hclgevf_wq = alloc_workqueue("%s", 0, 0, HCLGEVF_NAME);
> +
> if (!hclgevf_wq) {
> pr_err("%s: failed to create workqueue\n", HCLGEVF_NAME);
> return -ENOMEM;
> --
> 2.8.1
>
next prev parent reply other threads:[~2021-07-20 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 8:34 [PATCH RFC] net: hns3: add a module parameter wq_unbound Yufeng Mo
2021-07-20 9:01 ` Leon Romanovsky [this message]
2021-07-20 9:29 ` moyufeng
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=YPaQ0qW+uIToEM6c@unreal \
--to=leon@kernel.org \
--cc=chenhao288@hisilicon.com \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=linuxarm@huawei.com \
--cc=linuxarm@openeuler.org \
--cc=linyunsheng@huawei.com \
--cc=lipeng321@huawei.com \
--cc=moyufeng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=shenjian15@huawei.com \
--cc=yisen.zhuang@huawei.com \
--cc=zhangjiaran@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