From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] KNI discussion in userspace event
Date: Fri, 28 Oct 2016 17:13:23 +0200 [thread overview]
Message-ID: <16238883.tkNBRrfWjK@xps13> (raw)
In-Reply-To: <8c7f9d25-b042-6b7e-b197-7873ea7425ef@intel.com>
2016-10-28 15:31, Ferruh Yigit:
> * virtio-user + vhost-net
> This can be valid alternative, removes the out of tree kernel module
> need. But missing control path. Proof of concept work will be done.
That's probably a smart alternative for packet injection.
What do you mean exactly by "missing control path"?
> * Remove ethtool support ?
That's the other part of KNI.
It works only for e1000/ixgbe. That's a niche.
> Still there is some interest, will keep it. But not able to extend it to
> other drivers with current design.
It should be removed one day.
We must seriously think about a generic alternative.
Either we add DPDK support in ethtool or we create a dpdk-ethtool.
(or at least a library as the one in examples/).
Or we do nothing and wait to have more hardware like Mellanox supporting
a kernel bifurcated driver approach.
> *KNI PMD
> Patch is in the mail list, missing comments. If it gets some
> interest/comments/acks it may go in to next release.
I'm not against KNI PMD but it looks strange to add more support
to an old dying approach.
next prev parent reply other threads:[~2016-10-28 15:13 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 [this message]
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
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=16238883.tkNBRrfWjK@xps13 \
--to=thomas.monjalon@6wind.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).