DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Pernas Maradei <nico@emutex.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] White listing a virtual device
Date: Fri, 07 Nov 2014 13:13:37 +0000	[thread overview]
Message-ID: <545CC581.40309@emutex.com> (raw)
In-Reply-To: <2085190.a5sr9ou3P7@xps13>

On 07/11/14 12:55, Thomas Monjalon wrote:
> It's by design. If you add a vdev, you want to use it and there is no
> reason to whitelist it, and especially no reason to blacklist a device
> you created for your usage.
>
> Do you agree?

Hi Thomas,

Generally speaking you probably won't want to white list a virtual 
device - just using it. However it does seem an inconsistency in the 
design that you could add virtual devices but you can't white list them. 
If they are added to the main device list they should be treated just as 
another device.

In our particular use case we want to white list a pcap device to ensure 
that it is the only available port for testing.

Thanks,
Nico.

  reply	other threads:[~2014-11-07 13:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 12:36 Nicolas Pernas Maradei
2014-11-07 12:55 ` Thomas Monjalon
2014-11-07 13:13   ` Nicolas Pernas Maradei [this message]
2014-11-07 13:26     ` Neil Horman
2014-11-07 13:39       ` Nicolas Pernas Maradei
2014-11-07 13:59         ` Thomas Monjalon
2014-11-07 14:02         ` Neil Horman
2014-11-07 14:28           ` Nicolas Pernas Maradei
2014-11-07 14:57             ` Thomas Monjalon
2014-11-07 15:01               ` Nicolas Pernas Maradei
2014-11-10  8:13             ` Olivier MATZ
2014-11-16 21:07               ` Nicolas Pernas Maradei

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=545CC581.40309@emutex.com \
    --to=nico@emutex.com \
    --cc=dev@dpdk.org \
    --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).