DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Nicolas Pernas Maradei <nico@emutex.com>
Cc: dev@dpdk.org,
	"Nicolás Pernas Maradei" <nicolas.pernas.maradei@emutex.com>
Subject: Re: [dpdk-dev] [PATCH] eal: allow virtual devices to be white/black listed
Date: Mon, 17 Nov 2014 11:00:41 -0500	[thread overview]
Message-ID: <20141117160041.GF17886@hmsreliant.think-freely.org> (raw)
In-Reply-To: <546A0BA2.3040306@emutex.com>

On Mon, Nov 17, 2014 at 02:52:18PM +0000, Nicolas Pernas Maradei wrote:
> 
> On 17/11/14 14:10, Neil Horman wrote:
> >What are the above pci bus/device/function tuples?
> Hi,
> 
> I'm not sure if I understand the question. If you mean what kind of devices
> those are, as in physical or virtual, they are physical.
> rte_eal_devargs_add() would parse the string as a PCI ID. If it succeed it'd
> add them as physical devices having the field is_vdev = 0.
> 
> Please let me know if I answered your question.
> 
I get that, I was more asking, why those values?  They seem a bit magic to me,
and might benefit from some descriptive macros or comments so they make more
sense
Neil

> Thanks,
> Nico.
> 

  parent reply	other threads:[~2014-11-17 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-16 21:26 Nicolás Pernas Maradei
2014-11-17 14:10 ` Neil Horman
2014-11-17 14:58   ` Nicolas Pernas Maradei
     [not found]   ` <546A0BA2.3040306@emutex.com>
2014-11-17 16:00     ` Neil Horman [this message]
2014-11-17 16:40       ` Nicolas Pernas Maradei
2014-11-17 16:52         ` Bruce Richardson
2014-11-17 21:17           ` Neil Horman

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=20141117160041.GF17886@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=nico@emutex.com \
    --cc=nicolas.pernas.maradei@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).