From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: amin.tootoonchian@intel.com,
Marcin Kerlin <marcinx.kerlin@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment
Date: Mon, 4 Sep 2017 15:53:23 +0100 [thread overview]
Message-ID: <4abb6aa8-7b3c-5c98-5cb5-3bfbdefac4ea@intel.com> (raw)
In-Reply-To: <5905C8E33883CA46A8878E2D7724E21518CB6C@ORSMSX109.amr.corp.intel.com>
Hi,
On 24/08/2016 23:17, amin.tootoonchian at intel.com (Tootoonchian, Amin)
wrote:
> Sergio, could you please review this patch?
>
> Thanks,
> Amin
The patch status should be updated to 'Not Applicable' since similar
functionality has been implemented (commit d948f596).
Only Primary processes are allowed to call rte_eth_dev_allocate(), while
Secondary processes should call rte_eth_dev_attach_secondary()
Thanks,
Sergio
>> -----Original Message-----
>> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
>> Sent: Wednesday, July 20, 2016 8:12 AM
>> To: Tootoonchian, Amin <amin.tootoonchian at intel.com>
>> Cc: dev at dpdk.org; Kerlin, MarcinX <marcinx.kerlin at intel.com>
>> Subject: Re: [dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment
>>
>> Hi,
>>
>> 2016-07-20 15:07, Tootoonchian, Amin:
>>> Thomas, your thoughts?
>> I have 2 thoughts:
>> - it is too big for 16.07
>> - it is related to multi-process mechanism, maintained by Sergio ;)
>>
>> Sorry I won't look at it shortly.
next prev parent reply other threads:[~2017-09-04 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 2:01 Tootoonchian, Amin
2016-07-20 8:51 ` Kerlin, MarcinX
2016-07-20 15:07 ` Tootoonchian, Amin
2016-07-20 15:11 ` Thomas Monjalon
2016-07-20 17:25 ` Tootoonchian, Amin
2016-08-24 22:17 ` Tootoonchian, Amin
2017-09-04 14:53 ` Sergio Gonzalez Monroy [this message]
2018-12-21 15:30 ` Ferruh Yigit
2016-07-21 13:54 ` Kerlin, MarcinX
2016-07-22 19:56 ` Tootoonchian, Amin
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=4abb6aa8-7b3c-5c98-5cb5-3bfbdefac4ea@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=amin.tootoonchian@intel.com \
--cc=dev@dpdk.org \
--cc=marcinx.kerlin@intel.com \
--cc=thomas.monjalon@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).