DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Sujith Sankar (ssujith)" <ssujith@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Questions on use of multiple NIC interfaces
Date: Fri, 28 Mar 2014 09:25:33 +0000	[thread overview]
Message-ID: <CF5B3DE5.15605%ssujith@cisco.com> (raw)

Hi all,

Could someone answer the following questions about the usage of multiple NIC interfaces with DPDK?

1.  If my server has two identical Intel NICs, could I use both with DPDK and its applications?
2.  If both the NIC cards could be used with DPDK, could I use them with separate instances of applications?  E.g., NIC1 used by App1 and NIC2 used by App2.
3.  If answer to qn no 2 is yes, does the driver take care to avoid reinitialising NIC1 when App2 tries to initialise NIC2?  From what I’ve seen, DPDK calls the driver init for all the matching devices (vendor id and device id).

Thanks,
-Sujith

             reply	other threads:[~2014-03-28  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28  9:25 Sujith Sankar (ssujith) [this message]
2014-03-28  9:43 ` Vladimir Medvedkin
2014-03-28 10:02   ` Sujith Sankar (ssujith)

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=CF5B3DE5.15605%ssujith@cisco.com \
    --to=ssujith@cisco.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).