DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: support using 0 as coremask for no-affinitization
Date: Wed, 14 Apr 2021 09:29:38 -0700	[thread overview]
Message-ID: <20210414092938.22d017a8@hermes.local> (raw)
In-Reply-To: <CAJFAV8xd9m8QUEXe5eP3RncgOCf+u_1QSQuKENDqn40pWu-yVA@mail.gmail.com>

On Wed, 14 Apr 2021 18:15:34 +0200
David Marchand <david.marchand@redhat.com> wrote:

> On Tue, Feb 16, 2021 at 10:52 AM Bruce Richardson
> <bruce.richardson@intel.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...

  reply	other threads:[~2021-04-14 16:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16  9:43 Bruce Richardson
2021-02-16  9:51 ` Bruce Richardson
2021-04-14 16:15   ` David Marchand
2021-04-14 16:29     ` Stephen Hemminger [this message]
2021-04-14 17:02       ` Bruce Richardson
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

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=20210414092938.22d017a8@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.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).