DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org, Helin Zhang <helin.zhang@intel.com>
Subject: [dpdk-dev] BUG - KNI broken in 4.2 kernel
Date: Wed, 26 Aug 2015 17:15:16 -0700	[thread overview]
Message-ID: <20150826171516.7160bcb2@urahara> (raw)

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

No wonder they can't stay in sync.

             reply	other threads:[~2015-08-27  0:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27  0:15 Stephen Hemminger [this message]
2015-08-27  8:41 ` Thomas Monjalon
2015-08-27  9:58   ` De Lara Guarch, Pablo
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=20150826171516.7160bcb2@urahara \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.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).