patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: jerinj@marvell.com, 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>,
	"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 09:36:26 +0200	[thread overview]
Message-ID: <CAJFAV8xFwmjS9n85=dSVdgag5omG+J3ZofTyY2ahsTz_-j=o0w@mail.gmail.com> (raw)
In-Reply-To: <CALBAE1Pms_E26L5G-UDLt07mz7bCJf1Pn-K+dJecgCi=zbzc_A@mail.gmail.com>

On Wed, Oct 4, 2023 at 8:43 AM Jerin Jacob <jerinjacobk@gmail.com> wrote:
> > > 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?
>
> Yes, as mentioned in git commit log. Are 19 characters  OK, right? If

The commitlog was ambiguous.

> not, I will reduce it, "outb-poll" too generic.

The thread name max length in pthread API is 16 bytes (including the
trailing \0).

Besides, looking again at this driver, I suspect Thomas missed it
because of the plt_ prefix, when doing ce703c47de95 ("eal: force
prefix for internal threads").
Converting to the internal API would restrict the name down to 11
bytes (including \0).


-- 
David Marchand


  reply	other threads:[~2023-10-04  7:36 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
2023-10-04  6:41   ` Jerin Jacob
2023-10-04  7:36     ` David Marchand [this message]
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='CAJFAV8xFwmjS9n85=dSVdgag5omG+J3ZofTyY2ahsTz_-j=o0w@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.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).