From: David Marchand <david.marchand@redhat.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev <dev@dpdk.org>, Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] eal: store control thread CPU affinity in TLS
Date: Wed, 25 Mar 2020 13:53:26 +0100 [thread overview]
Message-ID: <CAJFAV8xvwtCYSRtfhV=HaeBoHUKs6Ke0FuCboMa-L8_+cW68vg@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ypt0VrXkrFn=zOLK6qm-C_yWaEcHEbhmz653r0TGaLHQ@mail.gmail.com>
On Fri, Mar 13, 2020 at 9:34 AM David Marchand
<david.marchand@redhat.com> wrote:
> On Wed, Feb 5, 2020 at 11:24 AM <jerinj@marvell.com> wrote:
> >
> > From: Jerin Jacob <jerinj@marvell.com>
> >
> > _cpuset TLS variable stores the CPU affinity of eal thread.
> > Populate the _cpuset TLS variable for control thread to
> >
> > 1) Make rte_thread_get_affinity() and eal_thread_dump_affinity
> > functional with control thread.
> > 2) Quick access to cpu affinity.
> >
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> Reviewed-by: David Marchand <david.marchand@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2020-03-25 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 10:24 jerinj
2020-03-13 8:34 ` David Marchand
2020-03-25 12:53 ` David Marchand [this message]
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='CAJFAV8xvwtCYSRtfhV=HaeBoHUKs6Ke0FuCboMa-L8_+cW68vg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=olivier.matz@6wind.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;
as well as URLs for NNTP newsgroup(s).