From: Nicolas Pernas Maradei <nicolas.pernas.maradei-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
To: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org,
"Nicolás Pernas Maradei"
<nico-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] eal: allow virtual devices to be white/black listed
Date: Mon, 17 Nov 2014 14:58:34 +0000 [thread overview]
Message-ID: <546A0D1A.2080702@emutex.com> (raw)
In-Reply-To: <20141117141050.GD17886-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
On 17/11/14 14:10, Neil Horman wrote:
> What are the above pci bus/device/function tuples?
>
> Neil
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.
Thanks,
Nico.
next prev parent reply other threads:[~2014-11-17 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 21:26 [PATCH] eal: allow virtual devices to be white/black listed Nicolás Pernas Maradei
[not found] ` <1416173215-27533-1-git-send-email-nicolas.pernas.maradei-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-17 14:10 ` Neil Horman
[not found] ` <20141117141050.GD17886-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-11-17 14:58 ` Nicolas Pernas Maradei [this message]
[not found] ` <546A0BA2.3040306@emutex.com>
[not found] ` <546A0BA2.3040306-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-17 16:00 ` Neil Horman
[not found] ` <20141117160041.GF17886-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-11-17 16:40 ` Nicolas Pernas Maradei
[not found] ` <546A24F3.4080107-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
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=546A0D1A.2080702@emutex.com \
--to=nicolas.pernas.maradei-m3nbujlqch7qt0dzr+alfa@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=nico-M3NBUjLqch7QT0dZR+AlfA@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.