From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Panu Matilainen <pmatilai@redhat.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, David Marchand <david.marchand@6wind.com>,
Helin Zhang <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] slow data path communication between DPDK port and Linux
Date: Wed, 16 Mar 2016 16:15:24 +0100 [thread overview]
Message-ID: <1909241.8RRZd4veSo@xps13> (raw)
In-Reply-To: <56E975DA.8030300@redhat.com>
2016-03-16 17:03, Panu Matilainen:
> On 03/16/2016 03:58 PM, Thomas Monjalon wrote:
> > 2016-03-16 15:15, Panu Matilainen:
> >> What I really would like to see is a clear policy regarding kernel
> >> modules in DPDK. I certainly am in no position to dictate one, and
> >> that's why I've been asking questions and throwing around crazy (or not)
> >> ideas around the topic.
> >
> > I think the consensus is to avoid new kernel module,
> > but allow them in a staging directory while being discussed upstream.
>
> To me the more interesting question is: what happens after that?
> As in, if upstream says no, does it mean axe from dpdk, no ifs and buts?
> If accepted upstream, does a version of the module still live within
> dpdk codebase (for example to provide the version for older kernel
> versions, I dont see that as unreasonable at all)?
>
>
> > About the existing out-of-tree kernel modules, we must continue trying
> > to obsolete them with upstream work.
>
> Agreed.
>
> >
> > If you feel the consensus must be clearly stated and acked,
> > please send a patch for doc/guides/contributing/design.rst.
>
> I'll be happy to, once we have a clear consensus on what the policy
> actually is.
Sending a patch is the most efficient way of having the discussion
happens with more contributors.
We, as a technical community, take some patch-based decisions ;)
next prev parent reply other threads:[~2016-03-16 15:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 16:32 [dpdk-dev] [PATCH " Ferruh Yigit
2016-01-27 16:32 ` [dpdk-dev] [PATCH 1/2] kdp: add kernel data path kernel module Ferruh Yigit
2016-02-08 17:14 ` Reshma Pattan
2016-02-09 10:53 ` Ferruh Yigit
2016-01-27 16:32 ` [dpdk-dev] [PATCH 2/2] kdp: add virtual PMD for kernel slow data path communication Ferruh Yigit
2016-01-28 8:16 ` Xu, Qian Q
2016-01-29 16:04 ` Yigit, Ferruh
2016-02-09 17:33 ` Reshma Pattan
2016-02-09 17:51 ` Ferruh Yigit
2016-02-19 5:05 ` [dpdk-dev] [PATCH v2 0/2] slow data path communication between DPDK port and Linux Ferruh Yigit
2016-02-19 5:05 ` [dpdk-dev] [PATCH v2 1/2] kdp: add kernel data path kernel module Ferruh Yigit
2016-02-19 5:05 ` [dpdk-dev] [PATCH v2 2/2] kdp: add virtual PMD for kernel slow data path communication Ferruh Yigit
2016-03-09 11:17 ` [dpdk-dev] [PATCH v3 0/2] slow data path communication between DPDK port and Linux Ferruh Yigit
2016-03-09 11:17 ` [dpdk-dev] [PATCH v3 1/2] kdp: add kernel data path kernel module Ferruh Yigit
2016-03-09 11:17 ` [dpdk-dev] [PATCH v3 2/2] kdp: add virtual PMD for kernel slow data path communication Ferruh Yigit
2016-03-14 15:32 ` [dpdk-dev] [PATCH v3 0/2] slow data path communication between DPDK port and Linux Ferruh Yigit
2016-03-16 7:26 ` Panu Matilainen
2016-03-16 8:19 ` Ferruh Yigit
2016-03-16 8:22 ` Panu Matilainen
2016-03-16 10:26 ` Ferruh Yigit
2016-03-16 10:45 ` Thomas Monjalon
2016-03-16 11:07 ` Mcnamara, John
2016-03-16 11:13 ` Ferruh Yigit
2016-03-16 13:23 ` Panu Matilainen
2016-03-16 13:15 ` Panu Matilainen
2016-03-16 13:58 ` Thomas Monjalon
2016-03-16 15:03 ` Panu Matilainen
2016-03-16 15:15 ` Thomas Monjalon [this message]
2016-03-16 11:07 ` 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=1909241.8RRZd4veSo@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.com \
--cc=pmatilai@redhat.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).