From: raman geetha gopalakrishnan <glowingsun@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, users <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] Reg DPDK with unsupported NIC
Date: Tue, 14 Mar 2017 15:43:24 +0530 [thread overview]
Message-ID: <CABAuC==s1MN0MO5z44yuirZBDpGQxFv4ybEBWFUY3wnTeC=JsQ@mail.gmail.com> (raw)
In-Reply-To: <337ACF7A-3802-4534-B0B9-9914F2DD3A97@intel.com>
Thanks Keith For the quick Reply.
On Tue, Mar 14, 2017 at 3:22 PM, Wiles, Keith <keith.wiles@intel.com> wrote:
>
>
> Sent from my iPhone
>
> > On Mar 14, 2017, at 5:29 PM, raman geetha gopalakrishnan <
> glowingsun@gmail.com> 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?
> >
> > In what way i can still develop DPDK APP with non supported NIC till get
> > the DPDK NIC.
>
> Take a look at the TAP PMD driver and look at the doc file in the doc
> directory.
>
> It will not be high performance but it can work nicely using tap and some
> like socat.
> >
> > Thanks
> > Raman
>
next prev parent reply other threads:[~2017-03-14 10:13 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 [this message]
2017-03-14 12:07 ` Ferruh Yigit
2017-03-15 4:45 ` Bruce Richardson
2017-03-15 5:24 ` Stephen Hemminger
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='CABAuC==s1MN0MO5z44yuirZBDpGQxFv4ybEBWFUY3wnTeC=JsQ@mail.gmail.com' \
--to=glowingsun@gmail.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.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).