From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] BUG - KNI broken in 4.2 kernel
Date: Thu, 27 Aug 2015 09:58:12 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C7EDDBE@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <2977472.7tFezkZAUv@xps13>
Hi Thomas, Stephen
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, August 27, 2015 9:42 AM
> To: Stephen Hemminger
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] BUG - KNI broken in 4.2 kernel
>
> 2015-08-26 17:15, Stephen Hemminger:
> > The network device ops handles changed again.
> >
> > Does KNI really need to keep yet another copy of the Intel driver code.
> > There already are 4 versions:
> > 1. Out-of tree base driver
> > 2. In-kernel mainline Linux driver
> > 3. DPDK driver
> > 4. KNI DPDK driver
>
> You forgot the BSD drivers and probably others.
>
> > No wonder they can't stay in sync.
>
> A patch to remove igb/ixgbe drivers from KNI would be welcome.
I have a patch ready to submit, I was just waiting for the kernel 4.2 to be released.
I will send the patch anyway, as the kernel is almost stable now (RC8),
so DPDK will not be broken when kernel is released.
Pablo
next prev parent reply other threads:[~2015-08-27 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 0:15 Stephen Hemminger
2015-08-27 8:41 ` Thomas Monjalon
2015-08-27 9:58 ` De Lara Guarch, Pablo [this message]
2015-08-27 15:23 ` Zhang, Helin
2015-08-27 15:49 ` Jay Rolette
2015-08-27 15:56 ` Zhang, Helin
2015-08-27 17:45 ` Stephen Hemminger
2015-08-27 17:53 ` Zhang, Helin
2015-08-28 12:44 ` Bruce Richardson
2015-08-28 15:48 ` Stephen Hemminger
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=E115CCD9D858EF4F90C690B0DCB4D8973C7EDDBE@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).