DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] KNI - issues
Date: Mon, 22 Feb 2016 14:00:02 +0000	[thread overview]
Message-ID: <20160222140002.GA10693@sivlogin002.ir.intel.com> (raw)
In-Reply-To: <20160220170708.37d0db29@xeon-e3>

On Sat, Feb 20, 2016 at 05:07:08PM -0800, Stephen Hemminger wrote:
> Is anyone working on making KNI conform to current kernel best practices
> and attempt to get it upstream?  After 2 minute code review I already
> see lots and lots of things that need work.

Hi Stephen,

I am working on not KNI, but on KNI enhancements: KCP and KDP.

KCP: Kernel Control Path
http://dpdk.org/dev/patchwork/patch/10481/

KDP: Kernel Data Path
http://dpdk.org/dev/patchwork/patch/10667/

Both are based on KNI, and KNI responsibilities split into these two modules, if these cover customer requirements, they can replace current KNI.
KCP: Common Linux tools support without kernel drivers inside KNI required.
KDP: Slow data path communication as PMD, supports both KNI FIFO and tap device.

And in mail list, problems of using out-of-tree kernel module mentioned a few times,
I can take over the task to submit a generic solution to Linux upstream, as a follow up to KCP and KDP tasks,
but I need some kind of experts feedback about feasibility of this work.

That is why I have sent a call to mail list about this issue:
http://dpdk.org/ml/archives/dev/2016-February/033279.html

Thanks to Aaron, he provided his support.

I would like to get your idea too.
Specially I am planning to use rtnetlink and as iproute2 maintainer I believe you already have some answers I am looking for.

Thanks,
ferruh

      parent reply	other threads:[~2016-02-22 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21  1:07 Stephen Hemminger
2016-02-22  2:44 ` Zhang, Helin
2016-02-22 14:00 ` Ferruh Yigit [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=20160222140002.GA10693@sivlogin002.ir.intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).