From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Panu Matilainen <pmatilai@redhat.com>,
David Marchand <david.marchand@6wind.com>,
"Zhang, Helin" <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 11:07:54 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202489E6B@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2637434.UE2LQEG9YB@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, March 16, 2016 10:46 AM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>
> Cc: dev@dpdk.org; Panu Matilainen <pmatilai@redhat.com>; David
> Marchand <david.marchand@6wind.com>; Zhang, Helin
> <helin.zhang@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v3 0/2] slow data path communication
> between DPDK port and Linux
> >
> > We can't remove it.
>
> Why?
There are a lot of people using KNI.
> > We can't replace/improve it -you were one of the major opposition to this.
> > This doesn't leave more option other than using it.
>
> Why cannot we replace it by something upstream?
In theory it could be upstreamed. Let's see how we get on with upstreaming the KCP component first.
John
next prev parent reply other threads:[~2016-03-16 11:07 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 [this message]
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
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=B27915DBBA3421428155699D51E4CFE202489E6B@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.com \
--cc=pmatilai@redhat.com \
--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).