DPDK patches and discussions
 help / color / mirror / Atom feed
From: "TSADOK, Shlomi (Shlomi)" <shlomi.tsadok@alcatel-lucent.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Specific NIC for DPDK?
Date: Mon, 6 Jan 2014 12:05:04 +0000	[thread overview]
Message-ID: <70ED7DF10DA6754880C553B2CD6E25230AB45B@FR712WXCHMBA13.zeu.alcatel-lucent.com> (raw)

Hello

A quick general question:

Is there a requirement for using a specific NIC/Chipset for DPDK or any NIC will do?

If there's such a requirement, why is that? Are the're any hardware optimizations etc. in DPDK enabled NICs?

Thanks

Shlomi

             reply	other threads:[~2014-01-06 12:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 12:05 TSADOK, Shlomi (Shlomi) [this message]
2014-01-06 13:31 ` Daniel Kaminsky
2014-01-06 15:38   ` Thomas Monjalon
2014-01-06 15:41     ` TSADOK, Shlomi (Shlomi)
2014-01-06 16:04       ` Thomas Monjalon
2014-01-06 16:23       ` St Leger, Jim
2014-01-06 16:25         ` TSADOK, Shlomi (Shlomi)

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=70ED7DF10DA6754880C553B2CD6E25230AB45B@FR712WXCHMBA13.zeu.alcatel-lucent.com \
    --to=shlomi.tsadok@alcatel-lucent.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).