From: Ben Hutchings <bhutchings@solarflare.com>
To: "Duyck, Alexander H" <alexander.h.duyck@intel.com>
Cc: David Miller <davem@davemloft.net>,
"santwona.behera@sun.com" <santwona.behera@sun.com>,
"jeff@garzik.org" <jeff@garzik.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Question on RX packet classification in ethtool userspace
Date: Wed, 19 Jan 2011 23:19:29 +0000 [thread overview]
Message-ID: <1295479169.2906.53.camel@localhost> (raw)
In-Reply-To: <80769D7B14936844A23C0C43D9FBCF0F25C04CB6B2@orsmsx501.amr.corp.intel.com>
On Wed, 2011-01-19 at 14:52 -0800, Duyck, Alexander H wrote:
> So I was looking into the option of replacing the ETHTOOL_GRXNTUPLE
> call with something like ETHTOOL_GRXCLSRLALL and it seems like I
> wasn't having much luck finding the userspace implementation in the
> ethtool.
I wasn't aware until now that there was a public implementation!
> I eventually found a patch in patchwork at
> http://patchwork.ozlabs.org/patch/23223/ which is supposed to add
> support but the current ethtool git tree doesn't appear to contain
> this code. I was wondering if I am missing something and it is on a
> branch somewhere, or is this something that was not applied to the
> userspace for some specific reason?
Thanks for digging this up. It's not in any branch that I know of. I'm
about to go on vacation, but I'll look at it when I get back. I would
appreciate it if someone would refresh the patch against current ethtool
(preferably reusing some of the functions added for the RX n-tuple
operations).
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-01-19 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 22:52 Question on RX packet classification in ethtool userspace Duyck, Alexander H
2011-01-19 23:19 ` Ben Hutchings [this message]
2011-01-20 17:24 ` Alexander H Duyck
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=1295479169.2906.53.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=santwona.behera@sun.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.