From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC 0/2] slow data path communication between DPDK port and Linux
Date: Fri, 22 Jan 2016 16:56:15 +0000 [thread overview]
Message-ID: <20160122165615.GA31579@sivlogin002.ir.intel.com> (raw)
In-Reply-To: <1881890.o9IDb9bZGc@xps13>
On Fri, Jan 22, 2016 at 05:31:45PM +0100, Thomas Monjalon wrote:
> Hi Ferruh,
>
> Not commenting the implementation, just the method.
>
> 2016-01-22 16:00, Ferruh Yigit:
> > This is slow data path communication implementation based on existing KNI.
> > Difference is: librte_kni converted into a PMD, kdp kernel module is almost
> > same except all control path functionality removed and some simplification done.
>
> Is there a chance to submit such kernel module on LKML instead of DPDK?
> We should avoid maintaining some out-of-tree modules.
The ones I have sent are not generic enough to be in Linux tree.
We already maintain kni kernel module, these patches are part of effort to make
kni more maintainable, by separation of concerns, removing network drivers from it,
and simplifying some of code.
For this patch set, tun/tap interface can be alternative, and it looks like it
removes out-of-tree kernel module requirement, unless people want current
FIFO implementation because of better performance.
For control path, unfortunately I am not aware of any solution without out-of-tree
kernel module support.
Thanks,
ferruh
next prev parent reply other threads:[~2016-01-22 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 16:00 Ferruh Yigit
2016-01-22 16:00 ` [dpdk-dev] [RFC 1/2] kdp: add kernel data path kernel module Ferruh Yigit
2016-01-22 16:00 ` [dpdk-dev] [RFC 2/2] kdp: add virtual PMD for kernel slow data path communication Ferruh Yigit
2016-01-22 16:31 ` [dpdk-dev] [RFC 0/2] slow data path communication between DPDK port and Linux Thomas Monjalon
2016-01-22 16:56 ` Ferruh Yigit [this message]
2016-01-22 17:15 ` Thomas Monjalon
2016-01-23 16:14 ` Bruce Richardson
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=20160122165615.GA31579@sivlogin002.ir.intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).