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

2014-11-07 13:39, Nicolas Pernas Maradei:
> On 07/11/14 13:26, Neil Horman wrote:
> > Then you create the pcap device with --vdev, and simply don't load the pmds for
> > any of your physical devices (or just don't use pci-whitelist at all if you're
> > doing a static build).  If you do that, then the corresponding niantic driver
> > won't initialize any of the hardware, you'll only get the pcap port.
> 
> What you are saying is just another way to black list the ports I don't 
> want to use. I'm aware of that option (as well as using the -b option) 
> but in our particular case we have several systems under test with 
> different configurations and we want to use this virtual port only. 
> Which seems to be a perfect use case for white listing rather than black 
> listing or modifying the system configuration.

Sorry I don't understand why you don't want to use the blacklist option.

-- 
Thomas

  reply	other threads:[~2014-11-07 13:49 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
2014-11-07 13:26     ` Neil Horman
2014-11-07 13:39       ` Nicolas Pernas Maradei
2014-11-07 13:59         ` Thomas Monjalon [this message]
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=2501357.jaIIFMyNbY@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nico@emutex.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).