DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] BUG - KNI broken in 4.2 kernel
Date: Fri, 28 Aug 2015 13:44:28 +0100	[thread overview]
Message-ID: <20150828124428.GA11184@bricha3-MOBL3> (raw)
In-Reply-To: <20150827104543.0138ab53@urahara>

On Thu, Aug 27, 2015 at 10:45:43AM -0700, Stephen Hemminger wrote:
> On Thu, 27 Aug 2015 15:56:16 +0000
> "Zhang, Helin" <helin.zhang@intel.com> wrote:
> 
> > Based on my experience, only one or two users asked for ethtool support, then we have it. Before that time, we don’t have KNI ethtool support.
> > I did not mean who uses KNI does not care about it, I mean for those users who don’t use KNI, they shouldn’t be bothered by the KNI compilation issues. That’s why I was thinking if we can disable it by default, but not remove it.
> >  
> > Regards,
> > Helin
> 
> Can KNI instead use DPDK hooks to provide generic ethtool semantics.
> That way it would work with all hardware.

Hi Stephen,

by this you mean that it's a generic library/kernel driver that acts as a proxy to make calls
into the ethdev library, rather than driver-specific calls? If so, that's an idea
that should be well worth pursuing. If it's something else you have in mind,
please clarify.

Thanks,

/Bruce

  parent reply	other threads:[~2015-08-28 12:44 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
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 [this message]
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=20150828124428.GA11184@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).