DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Tootoonchian, Amin" <amin.tootoonchian@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment
Date: Fri, 21 Dec 2018 15:30:31 +0000	[thread overview]
Message-ID: <2d87b129-0667-80a8-a0af-486d45aa9cd4@intel.com> (raw)
In-Reply-To: <4abb6aa8-7b3c-5c98-5cb5-3bfbdefac4ea@intel.com>

On 9/4/2017 3:53 PM, sergio.gonzalez.monroy at intel.com (Sergio Gonzalez
Monroy) wrote:
> 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()

Agreed with comment, and even after that comment many thing changed in multi
process support. Patch status updated as 'Not Applicable'.

> 
> 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.
> 
> 
> 

  reply	other threads:[~2018-12-21 15:30 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
2018-12-21 15:30           ` Ferruh Yigit [this message]
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=2d87b129-0667-80a8-a0af-486d45aa9cd4@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=amin.tootoonchian@intel.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).