From: Jason Kwon <m43kwon@gmail.com>
To: ALeX Wang <ee07b291@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Must kni be associated with a dpdk port?
Date: Thu, 31 Mar 2016 09:56:18 -0700 [thread overview]
Message-ID: <CAEo68aqWEw+9b1wnzZ047Btc1PFtEYJ36iWFyDvkwSAua3O4ZQ@mail.gmail.com> (raw)
In-Reply-To: <CANmyKO77eNM34m7hO-u+ODj-+sZA5vzTNmz7SDPA-kBD9Jvh-A@mail.gmail.com>
No, I don't think it is compulsory--I am using it in this way. You can
modify the example program to remove the references to the physical PCI
device and have the KNI instance created as a standalone device.
Alternatively, you can use something like librte_pmd_ring, a ring-based
poll-mode driver, to associate KNI with a purely software-based PMD. In
this case, you are associating KNI with a DPDK port, but no physical
Ethernet device.
Jason
On Wed, Mar 30, 2016 at 11:14 AM, ALeX Wang <ee07b291@gmail.com> 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,
>
> --
> Alex Wang,
>
prev parent reply other threads:[~2016-03-31 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 18:14 ALeX Wang
2016-03-31 16:56 ` Jason Kwon [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=CAEo68aqWEw+9b1wnzZ047Btc1PFtEYJ36iWFyDvkwSAua3O4ZQ@mail.gmail.com \
--to=m43kwon@gmail.com \
--cc=ee07b291@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).