DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix check when retrieving current cpu affinity
Date: Thu, 14 Feb 2019 18:41:38 +0100	[thread overview]
Message-ID: <CAJFAV8ya=_yQsCN5ok+t-+pkuhH=vEj1UY88O9pNev-R+AH3tA@mail.gmail.com> (raw)
In-Reply-To: <1fed1442-efc2-0156-7db1-8b2c01292659@intel.com>

On Thu, Feb 14, 2019 at 5:44 PM Burakov, Anatoly <anatoly.burakov@intel.com>
wrote:

> On 14-Feb-19 1:27 PM, David Marchand wrote:
> > pthread_getaffinity_np returns a >0 value when failing.
> >
> > This is mainly for the sake of correctness.
> > The only case where it could fail is when passing an incorrect cpuset
> > size wrt to the kernel.
> >
> > Fixes: 2eba8d21f3c9 ("eal: restrict cores auto detection")
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---
> >   lib/librte_eal/common/eal_common_options.c | 5 ++---
> >   1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/lib/librte_eal/common/eal_common_options.c
> b/lib/librte_eal/common/eal_common_options.c
> > index 6c96f45..1f45f82 100644
> > --- a/lib/librte_eal/common/eal_common_options.c
> > +++ b/lib/librte_eal/common/eal_common_options.c
> > @@ -1343,10 +1343,9 @@ static int xdigit2val(unsigned char c)
> >       unsigned int lcore_id;
> >       unsigned int removed = 0;
> >       rte_cpuset_t affinity_set;
> > -     pthread_t tid = pthread_self();
> >
> > -     if (pthread_getaffinity_np(tid, sizeof(rte_cpuset_t),
> > -                             &affinity_set) < 0)
> > +     if (pthread_getaffinity_np(pthread_self(), sizeof(rte_cpuset_t),
> > +                             &affinity_set))
> >               CPU_ZERO(&affinity_set);
> >
> >       for (lcore_id = 0; lcore_id < RTE_MAX_LCORE; lcore_id++) {
> >
> CC: stable?
>

Not really sure about CCing stable for this.

I did not get errors with pthread_getaffinity_np so far.
Afaiu, it would need the kernel and libc to have different cpuset sizes.
I did not investigate in which situations it could happen.


-- 
David Marchand

  reply	other threads:[~2019-02-14 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 13:27 David Marchand
2019-02-14 16:44 ` Burakov, Anatoly
2019-02-14 17:41   ` David Marchand [this message]
2019-02-19 11:40     ` Burakov, Anatoly
2019-02-19 11:55       ` David Marchand
2019-02-19 20:38 ` [dpdk-dev] [PATCH v2] " David Marchand
2019-02-20 16:02   ` Burakov, Anatoly
2019-03-07 15:36     ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-02-21 18:58   ` [dpdk-dev] " Rami Rosen

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='CAJFAV8ya=_yQsCN5ok+t-+pkuhH=vEj1UY88O9pNev-R+AH3tA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    /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).