From: Bruce Richardson <firstname.lastname@example.org>
To: Stephen Hemminger <email@example.com>
Cc: David Marchand <firstname.lastname@example.org>, dev <email@example.com>
Subject: Re: [dpdk-dev] [PATCH] eal: support using 0 as coremask for no-affinitization
Date: Wed, 14 Apr 2021 18:02:58 +0100 [thread overview]
Message-ID: <20210414170258.GF514@bricha3-MOBL.ger.corp.intel.com> (raw)
On Wed, Apr 14, 2021 at 09:29:38AM -0700, Stephen Hemminger wrote:
> On Wed, 14 Apr 2021 18:15:34 +0200
> David Marchand <firstname.lastname@example.org> wrote:
> > On Tue, Feb 16, 2021 at 10:52 AM Bruce Richardson
> > <email@example.com> wrote:
> > >
> > > On Tue, Feb 16, 2021 at 09:43:00AM +0000, Bruce Richardson wrote:
> > > > Allow the user to specify that they don't want any core pinning from DPDK
> > > > by passing in the coremask of 0.
> > > > ---
> > >
> > > Apologies, missed my signoff, will add in V2, but will wait for feedback on
> > > this V1 first.
> > I did not see a v2, is this still for 21.05?
> > What are the usecases for this feature?
> > I could think of using this in combination with external threads in
> > applications like OVS... ?
> It would cause lots of DPDK applications to discover the problems with
> preemption and priority inversion with DPDK spinlocks...
I'd actually be surprised. I would expect most apps that want this sort of
thing are already just using a single master core (perhaps with faked EAL
args) and adding their own threads on top of that. All this patch would do
is remove the requirement for that master lcore.
next prev parent reply other threads:[~2021-04-14 17:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 9:43 [dpdk-dev] [PATCH] eal: support using 0 as coremask for no-affinitization Bruce Richardson
2021-02-16 9:51 ` Bruce Richardson
2021-04-14 16:15 ` David Marchand
2021-04-14 16:29 ` Stephen Hemminger
2021-04-14 17:02 ` Bruce Richardson [this message]
2021-04-14 16:55 ` Bruce Richardson
2021-02-16 10:36 ` Burakov, Anatoly
2021-02-16 10:46 ` Bruce Richardson
2021-02-16 10:52 ` Burakov, Anatoly
2021-02-16 17:22 ` Van Haaren, Harry
2021-02-16 17:30 ` Bruce Richardson
2021-02-16 17:44 ` Van Haaren, Harry
2021-02-17 12:09 ` Burakov, Anatoly
2021-02-17 12:14 ` Van Haaren, Harry
2021-02-17 13:26 ` Bruce Richardson
2021-02-17 13:37 ` Burakov, Anatoly
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.