From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI discussion in userspace event
Date: Fri, 28 Oct 2016 09:25:25 -0700 [thread overview]
Message-ID: <20161028092525.696652d4@xeon-e3> (raw)
In-Reply-To: <8c7f9d25-b042-6b7e-b197-7873ea7425ef@intel.com>
On Fri, 28 Oct 2016 15:31:50 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Discussed alternatives were:
> * Tun/Tap
> This won't be as fast as KNI and performance is an issue.
That is a myth. Both require the some number of copies.
TUN/TAP copies is a syscall and KNI copies is a kthread.
Actually, the KNI method is worse because it has kernel thread
always running chewing a CPU. I.e it is pure poll mode.
next prev parent reply other threads:[~2016-10-28 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 14:31 Ferruh Yigit
2016-10-28 15:03 ` Igor Ryzhov
2016-10-28 15:13 ` Thomas Monjalon
2016-10-28 15:51 ` Richardson, Bruce
2016-10-28 16:13 ` Thomas Monjalon
2016-10-28 17:29 ` Igor Ryzhov
2016-10-28 18:40 ` Thomas Monjalon
2016-10-28 19:23 ` Igor Ryzhov
2016-10-28 23:09 ` Vincent Jardin
2016-10-28 16:25 ` Stephen Hemminger [this message]
2016-11-23 16:49 ` Aws Ismail
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=20161028092525.696652d4@xeon-e3 \
--to=stephen@networkplumber.org \
--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).