From: "Roger B. Melton" <rmelton@cisco.com>
To: David Marchand <david.marchand@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Don Provan <dprovan@bivio.net>
Subject: Re: [dpdk-dev] Making rte_eal_pci_probe() in rte_eal_init() optional?
Date: Sun, 15 Nov 2015 09:45:41 -0500 [thread overview]
Message-ID: <56489A95.1050706@cisco.com> (raw)
In-Reply-To: <CALwxeUvrN7CFbXQ013hFgp6aa3UcHjdrH1BjOm03VdzLLeD76w@mail.gmail.com>
Hi David,
We are on a very old kernel (2.6.xx) that lacks VFIO. In the future
however, after migration to a newer kernel it will be an option.
I like the "-b all" and "-w none" idea, but I think it might be
complicated to implement it the way we would need it to work. The
existing -b and -w options persist for the duration of the application,
and we would need the "-b all"/"-w none" to persists only through
rte_eal_init() time. Otherwise our attempt to to attach a device at a
later time would be blocked by the option.
Wouldn't it be simpler to have an option to disable the rte_eal_init()
time the probe. Would that address the issue with VFIO, prevent
automatically attaching to devices while permitting on demand attach?
Thanks again.
Regards,
-Roger
On 11/14/15 12:51 PM, David Marchand wrote:
> Hello Roger,
>
> On Sat, Nov 14, 2015 at 4:55 PM, Roger B. Melton <rmelton@cisco.com
> <mailto:rmelton@cisco.com>> wrote:
>
> Agreed. For our application, the debug case would be to _enable_
> the PCI scan.
>
> Again, thanks David for pointing it out. It did solve our problem.
>
>
> The only problem with --no-pci is that I think that vfio won't work
> properly if used.
>
> Did you try to blacklist all your devices then attach them later ?
> I would say what you need here is to "blacklist all" or "whitelist
> none" at startup, so maybe a special keyword for -b/-w options.
>
>
> --
> David Marchand
--
____________________________________________________________________
|Roger B. Melton | | Cisco Systems |
|CPP Software :|: :|: 7100 Kit Creek Rd |
|+1.919.476.2332 phone :|||: :|||: RTP, NC 27709-4987 |
|+1.919.392.1094 fax .:|||||||:..:|||||||:. rmelton@cisco.com |
| |
| This email may contain confidential and privileged material for the|
| sole use of the intended recipient. Any review, use, distribution |
| or disclosure by others is strictly prohibited. If you are not the |
| intended recipient (or authorized to receive for the recipient), |
| please contact the sender by reply email and delete all copies of |
| this message. |
| |
| For corporate legal information go to: |
| http://www.cisco.com/web/about/doing_business/legal/cri/index.html |
|__________________________ http://www.cisco.com ____________________|
next prev parent reply other threads:[~2015-11-15 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 22:58 Don Provan
2015-11-13 23:03 ` Jan Viktorin
2015-11-14 15:55 ` Roger B. Melton
2015-11-14 17:51 ` David Marchand
2015-11-15 14:45 ` Roger B. Melton [this message]
2015-11-16 9:46 ` David Marchand
2015-11-17 13:56 ` Roger B. Melton
2015-11-17 15:46 ` Thomas Monjalon
2015-11-18 22:13 ` Roger B. Melton
2015-11-21 12:54 ` Roger B. Melton
-- strict thread matches above, loose matches on Subject: below --
2015-11-12 22:43 Roger B Melton
2015-11-13 8:49 ` David Marchand
2015-11-13 12:07 ` Roger B. Melton
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=56489A95.1050706@cisco.com \
--to=rmelton@cisco.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=dprovan@bivio.net \
/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).