From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
raman geetha gopalakrishnan <glowingsun@gmail.com>,
dev@dpdk.org, users <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] Reg DPDK with unsupported NIC
Date: Tue, 14 Mar 2017 22:24:02 -0700 [thread overview]
Message-ID: <20170314222402.1648a719@xeon-e3> (raw)
In-Reply-To: <20170315044502.GA7360@bricha3-MOBL3.ger.corp.intel.com>
On Wed, 15 Mar 2017 04:45:03 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:
> On Tue, Mar 14, 2017 at 12:07:42PM +0000, Ferruh Yigit wrote:
> > On 3/14/2017 9:28 AM, raman geetha gopalakrishnan wrote:
> > > Hi ,
> > >
> > > Please find my query, Currently i am planning to develop DPDK APP (linux
> > > env). I do not have DPDK supported NIC. Till then i would still like to
> > > develop DPDK APP and want DPDK to use OS interface to TX/RX packets from
> > > NIC. How can i make it?
> >
> > > I went through KNI and my understanding is you
> > > cannot use it - is this correct?
> >
> > You can use it. KNI does not require a physical device at all.
> >
> > But with the KNI support in main tree, you need to use KNI specific
> > APIs, - which KNI sample app shows.
> >
> > With the KNI PMD in next-net tree, it is possible to use KNI as any
> > other device.
> >
>
> Just my 2c. While you can indeed use KNI here, I think I would recommend
> pcap or AF_PACKET as my first-choice options, with TAP also a
> possibility too, as Keith has already suggested.
>
> /Bruce
Other than development environment, why would you want to use DPDK with AF_PACKET
or TAP? It will be slower than kernel networking and with KNI doubly slow.
prev parent reply other threads:[~2017-03-15 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 9:28 [dpdk-users] " raman geetha gopalakrishnan
2017-03-14 9:46 ` [dpdk-users] [dpdk-dev] " Thomas Monjalon
2017-03-14 10:13 ` raman geetha gopalakrishnan
2017-03-14 9:52 ` Wiles, Keith
2017-03-14 10:13 ` raman geetha gopalakrishnan
2017-03-14 12:07 ` Ferruh Yigit
2017-03-15 4:45 ` Bruce Richardson
2017-03-15 5:24 ` Stephen Hemminger [this message]
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=20170314222402.1648a719@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=glowingsun@gmail.com \
--cc=users@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).