All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Pernas Maradei <nico-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
To: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: White listing a virtual device
Date: Fri, 07 Nov 2014 13:39:52 +0000	[thread overview]
Message-ID: <545CCBA8.7030900@emutex.com> (raw)
In-Reply-To: <20141107132618.GD25469-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>


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

Hi Neil,

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.

As far as I remember this option was available in previous versions.

Thanks,
Nico.

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 12:36 White listing a virtual device Nicolas Pernas Maradei
     [not found] ` <545CBCE0.2030806-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 12:55   ` Thomas Monjalon
2014-11-07 13:13     ` Nicolas Pernas Maradei
     [not found]       ` <545CC581.40309-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 13:26         ` Neil Horman
     [not found]           ` <20141107132618.GD25469-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-11-07 13:39             ` Nicolas Pernas Maradei [this message]
     [not found]               ` <545CCBA8.7030900-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 13:59                 ` Thomas Monjalon
2014-11-07 14:02                 ` Neil Horman
     [not found]                   ` <20141107140201.GE25469-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-11-07 14:28                     ` Nicolas Pernas Maradei
     [not found]                       ` <545CD710.4040406-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 14:57                         ` Thomas Monjalon
2014-11-07 15:01                           ` Nicolas Pernas Maradei
2014-11-10  8:13                         ` Olivier MATZ
     [not found]                           ` <546073A3.1000008-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
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=545CCBA8.7030900@emutex.com \
    --to=nico-m3nbujlqch7qt0dzr+alfa@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.