On Wed, Dec 07, 2022 at 08:07:16PM -0800, Stephen Hemminger wrote:
> On Wed, 7 Dec 2022 14:33:31 -0800
> Tyler Retzlaff wrote:
>
> > On Wed, Dec 07, 2022 at 01:03:41PM -0800, Stephen Hemminger wrote:
> > > On Wed, 7 Dec 2022 11:00:13 -0800
> > > Tyler Retzlaff wrote:
> > >
> > > > +static ch
On Wed, 7 Dec 2022 14:33:31 -0800
Tyler Retzlaff wrote:
> On Wed, Dec 07, 2022 at 01:03:41PM -0800, Stephen Hemminger wrote:
> > On Wed, 7 Dec 2022 11:00:13 -0800
> > Tyler Retzlaff wrote:
> >
> > > +static char lcore_names[RTE_MAX_LCORE][RTE_LCORE_NAME_MAX_LEN];
> >
> > This copy would r
On Wed, Dec 07, 2022 at 01:03:41PM -0800, Stephen Hemminger wrote:
> On Wed, 7 Dec 2022 11:00:13 -0800
> Tyler Retzlaff wrote:
>
> > +static char lcore_names[RTE_MAX_LCORE][RTE_LCORE_NAME_MAX_LEN];
>
> This copy would redundant on Linux.
>
> > +
> > +int
> > +rte_lcore_set_name(unsigned int lc
On Wed, 7 Dec 2022 11:00:13 -0800
Tyler Retzlaff wrote:
> +static char lcore_names[RTE_MAX_LCORE][RTE_LCORE_NAME_MAX_LEN];
This copy would redundant on Linux.
> +
> +int
> +rte_lcore_set_name(unsigned int lcore_id, const char *name)
> +{
> + if (unlikely(lcore_id >= RTE_MAX_LCORE))
> +
Add two new APIs that allow set and get of a name for an lcore that do
not explose platform thread details via the public interface.
If the underlying platform thread API does allow set of a name for the
lcore thread id it is called as a side-effect of set but lack of support
or failure from the p
5 matches
Mail list logo