DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Moon-Sang Lee <sang0627@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI port type in IP pipeline
Date: Wed, 20 Apr 2016 14:09:32 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126479A3CD0@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAACK=XdOQoDgLTFBa78ORsfCqFNcfKc=x7sTgqx=1EwMfohWPg@mail.gmail.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Moon-Sang Lee
> Sent: Friday, April 15, 2016 8:13 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] KNI port type in IP pipeline
> 
> According to pp. 145 of DPDK programmer's guide 2.2.0, the KNI port type is
> described in
> table 23.1. But, I cannot find any material about how to specify the KNI
> port type in pipeline
> configuration file.
> 
> Unfortunately, it seems there is no related source file in
> $DPDK_TOP/lib/librte_port.
> 
> Does packet framework already implement the KNI port type somewhere
> or should I implement that KNI port type by myself?
> 
> regards,
> 
> 
> 
> --
> Moon-Sang Lee, SW Engineer
> Email: sang0627@gmail.com
> Wisdom begins in wonder. *Socrates*

Hi,

There is no KNI or TUN/TAP port implemented in librte_port currently, hence please consider contributing this to DPDK. If the throughput of this device is not the first priority for you, I would actually recommend the TUN/TAP approach rather than KNI, as KNI seem to require significant maintenance due to constant changes in kernel header files, while TUN/TAP is very stable.

KNI and TUN/TAP could also be leveraged straight away by librte_port as rte_ethdev type of port if they would be made available as PMDs. I know there were some plans to make this happen, but for some reason looks like the plans did not become reality.

Thanks,
Cristian




      reply	other threads:[~2016-04-20 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  7:12 Moon-Sang Lee
2016-04-20 14:09 ` Dumitrescu, Cristian [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=3EB4FA525960D640B5BDFFD6A3D89126479A3CD0@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=sang0627@gmail.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).