From: Daniele Di Proietto <daniele.di.proietto@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Binding NICs while running DPDK app
Date: Thu, 19 Feb 2015 22:22:32 +0000 [thread overview]
Message-ID: <CAExiqTLLA_O5U1opkkKKFsEr36ivO4NrmY16Htpkmo8ak=K9Hw@mail.gmail.com> (raw)
Hi,
I would like to implement a scenario like the following:
- Some NICs are bound to the igb_uio driver
- A DPDK application is started and it sends/receives packet to/from those NICs.
- Another set of NICs are bound to the igb_uio driver.
- The same DPDK application continues processing packets from the old
NICs and starts processing packets from the new NICs as well.
I have done some tests and the DPDK application sees the new NICs
after a call to rte_eal_pci_probe(). Though I'm having some question:
- Can I call rte_eal_pci_probe() whenever I want? Will it interfere
with existing NICs' operations? (the documentation doesn't say much
about that)
- Will it work with DPDK 1.7 and DPDK 1.8? I'm asking because I've
noticed that in DPDK 1.7 rte_eal_pci_probe() checks if a NIC is
already registered, while in DPDK 1.8 this check has been removed.
I've seen that there's some work towards proper hotplug support, but I
was hoping to get the above (just adding, no removals) working with
current DPDK releases.
Thanks,
Daniele Di Proietto
reply other threads:[~2015-02-19 22:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAExiqTLLA_O5U1opkkKKFsEr36ivO4NrmY16Htpkmo8ak=K9Hw@mail.gmail.com' \
--to=daniele.di.proietto@gmail.com \
--cc=dev@dpdk.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 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).