From: ALeX Wang <ee07b291@gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Must kni be associated with a dpdk port?
Date: Thu, 31 Mar 2016 08:22:51 -0700 [thread overview]
Message-ID: <CANmyKO47MFHLxie0+Nbn6Z5QfJYXUX8-KY_Z-ntyvhnAmUOsyg@mail.gmail.com> (raw)
In-Reply-To: <56FCF415.6090301@intel.com>
Thx a lot, for the answer,!
Exactly what I'm looking for,~
On 31 March 2016 at 02:55, Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 3/30/2016 6:20 PM, ALeX Wang wrote:
> > Hi,
> >
> > I want to use 'rte_kni_alloc()' to create a kernel iface and
> > use it to test application rx. From the api and example in
> > 'examples/kni/main.c', i saw the 'conf' argument is assigned
> > with pci info of a dpdk port.
> >
> > Want to ask if this is compulsory... Must kni always be
> > used together with a dpdk port?
> >
> > Thanks,
> >
>
> Hi Alex,
>
> You don't have to associate kni with dpdk port.
>
> pci info is required for ethtool support, if you are only interested in
> data transfer, you don't have to provide pci information.
>
> Regards,
> ferruh
>
--
Alex Wang,
Open vSwitch developer
prev parent reply other threads:[~2016-03-31 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 17:20 ALeX Wang
2016-03-31 9:55 ` Ferruh Yigit
2016-03-31 15:22 ` ALeX Wang [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=CANmyKO47MFHLxie0+Nbn6Z5QfJYXUX8-KY_Z-ntyvhnAmUOsyg@mail.gmail.com \
--to=ee07b291@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).