From: David Marchand <david.marchand@redhat.com>
To: jerinj@marvell.com
Cc: dev@dpdk.org, "Nithin Dabilpuram" <ndabilpuram@marvell.com>,
"Kiran Kumar K" <kirankumark@marvell.com>,
"Sunil Kumar Kori" <skori@marvell.com>,
"Satha Rao" <skoteshwar@marvell.com>,
"Long Li" <longli@microsoft.com>,
"Tyler Retzlaff" <roretzla@linux.microsoft.com>,
"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Liron Himi" <lironh@marvell.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] common/cnxk: fix direct rte symbol usage
Date: Wed, 4 Oct 2023 08:03:30 +0200 [thread overview]
Message-ID: <CAJFAV8yto-ViG52B1pnPcoEOtu+XE-hbnzW80MvPAqyCdw4=8w@mail.gmail.com> (raw)
In-Reply-To: <20231003183956.1270510-1-jerinj@marvell.com>
Hello Jerin,
On Tue, Oct 3, 2023 at 8:40 PM <jerinj@marvell.com> wrote:
>
> From: Jerin Jacob <jerinj@marvell.com>
>
> The common code is shared between different driver environments,
> introduce missing plt_ abstractions of missing rte_ symbols and
> use plt symbols to avoid changing roc_* files.
>
> Also update the thread name for outbound soft expiry thread
> in a7ba40b2b1bf7.
>
> Fixes: 3d4e27fd7ff0 ("use abstracted bit count functions")
> Fixes: a7ba40b2b1bf ("drivers: convert to internal control threads")
> Fixes: c88d3638c7fc ("common/cnxk: support REE")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
- Could we add something in checkpatch for this driver?
I was aware of this s/rte_/plt_/ peculiarity but still missed it...
- If you want this backported in LTS, I suggest splitting the fix
against c88d3638c7fc ("common/cnxk: support REE") and the rest than
only affects current release.
- One comment:
> diff --git a/drivers/common/cnxk/roc_nix_inl_dev.c b/drivers/common/cnxk/roc_nix_inl_dev.c
> index 6aa191410b..614d0858e5 100644
> --- a/drivers/common/cnxk/roc_nix_inl_dev.c
> +++ b/drivers/common/cnxk/roc_nix_inl_dev.c
> @@ -826,7 +826,7 @@ nix_inl_outb_poll_thread_setup(struct nix_inl_dev *inl_dev)
> soft_exp_consumer_cnt = 0;
> soft_exp_poll_thread_exit = false;
> rc = plt_thread_create_control(&inl_dev->soft_exp_poll_thread,
> - "outb-poll", nix_inl_outb_poll_thread, inl_dev);
> + "outb-soft-exp-poll", nix_inl_outb_poll_thread, inl_dev);
Such a thread name is too long.
This is reverting Thomas change.
Is this intentional?
--
David Marchand
next prev parent reply other threads:[~2023-10-04 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 18:39 jerinj
2023-10-04 4:39 ` Nithin Dabilpuram
2023-10-04 6:03 ` David Marchand [this message]
2023-10-04 6:41 ` Jerin Jacob
2023-10-04 7:36 ` David Marchand
2023-10-04 7:47 ` Jerin Jacob
[not found] ` <20231004122432.3255418-1-jerinj@marvell.com>
2023-10-04 12:24 ` [dpdk-dev] [PATCH v2 2/2] common/cnxk: fix direct rte symbol usage in REE jerinj
2023-10-05 14:17 ` Jerin Jacob
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='CAJFAV8yto-ViG52B1pnPcoEOtu+XE-hbnzW80MvPAqyCdw4=8w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=lironh@marvell.com \
--cc=longli@microsoft.com \
--cc=mb@smartsharesystems.com \
--cc=ndabilpuram@marvell.com \
--cc=roretzla@linux.microsoft.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).