DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kiran KN <kirankn@juniper.net>
To: David Marchand <david.marchand@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] eal: changes for setting control thread mask
Date: Sat, 27 Mar 2021 18:54:48 +0000	[thread overview]
Message-ID: <0CF27587-A9D1-4B4F-B692-652BFB3288F0@juniper.net> (raw)
In-Reply-To: <CAJFAV8xA0raZWCTooDkUw1tzMR2+qn8ROu_3Ea=o_PA_sQrrvQ@mail.gmail.com>

Hi David,
This task was supposed to be taken up by someone else in my organisation. Will check and update.

Thanks

On 25/03/21, 8:21 PM, "David Marchand" <david.marchand@redhat.com> wrote:

    [External Email. Be cautious of content]


    On Tue, Apr 21, 2020 at 10:01 AM David Marchand
    <david.marchand@redhat.com> wrote:
    >
    > On Tue, Apr 21, 2020 at 9:42 AM Kiran KN <kirankn@juniper.net> wrote:
    > > Define a global variable ctrl_thread_set which the application can set.
    > > If this is the case, use this for setting control thread affinity instead
    > > of deducing it from the existing core pinning of the process.
    >
    > I am unconvinced on adding an EAL option for this.
    > It needs an explanation on why you can't rely on the dpdk process
    > current affinity for control threads.
    > And we will need a unit test.
    >
    > Please rebase your patch on master too.
    >
    > > signed-off-by: Kiran KN <kirankn@juniper.net>
    >
    > Signed-off-by*

    Is this patch abandoned?
    Thanks.

    --
    David Marchand



Juniper Business Use Only

      reply	other threads:[~2021-03-27 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  7:42 Kiran KN
2020-04-21  8:01 ` David Marchand
2021-03-25 14:51   ` David Marchand
2021-03-27 18:54     ` Kiran KN [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=0CF27587-A9D1-4B4F-B692-652BFB3288F0@juniper.net \
    --to=kirankn@juniper.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).