DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Li Han <han.li1@zte.com.cn>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	dev <dev@dpdk.org>,
	 Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: Re: [dpdk-dev] [PATCH] eal/linux: fix muti-secondary msl create issue
Date: Wed, 20 Nov 2019 08:36:37 +0100	[thread overview]
Message-ID: <CAJFAV8zZD3r=KA6gYEEhW7YmmNksYJTx4XsZcZyay98DY-dy3w@mail.gmail.com> (raw)
In-Reply-To: <1574214917-7700-1-git-send-email-han.li1@zte.com.cn>

On Wed, Nov 20, 2019 at 3:48 AM Li Han <han.li1@zte.com.cn> wrote:
>
> when we run dpdk in docker, process pid may the same.
> add rte_rdtsc() to ensure all the names used in rte_fbarray_init
> are different.

There is already a fix being prepared by Yasufumi Ogawa.
https://patchwork.dpdk.org/patch/62972/


-- 
David Marchand


  reply	other threads:[~2019-11-20  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20  1:55 Li Han
2019-11-20  7:36 ` David Marchand [this message]
2019-11-20 10:45 ` Ananyev, Konstantin

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='CAJFAV8zZD3r=KA6gYEEhW7YmmNksYJTx4XsZcZyay98DY-dy3w@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=han.li1@zte.com.cn \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    /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).