From: Ben Hutchings <bhutchings@solarflare•com>
To: Vladislav Zolotarov <vladz@broadcom•com>
Cc: Dimitris Michailidis <dm@chelsio•com>,
Peter Waskiewicz <peter.p.waskiewicz.jr@intel•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
David Miller <davem@davemloft•net>
Subject: Re: (Lack of) specification for RX n-tuple filtering
Date: Wed, 08 Dec 2010 19:14:41 +0000 [thread overview]
Message-ID: <1291835681.2560.53.camel@bwh-desktop> (raw)
In-Reply-To: <1291835453.24019.13.camel@lb-tlvb-vladz>
On Wed, 2010-12-08 at 21:10 +0200, Vladislav Zolotarov wrote:
> > The implementation of the -U
> > option could potentially be made to fallback to ETHTOOL_SRXCLSRLINS if
> > vlan_tag and user_def are not specified.
> >
>
> Having said that, don't u think that it could be more user friendly to
> extend the ETHTOOL_SRXCLSRLINS interface to handle the lan_tag and
> user_def and drop the n-tuple interface at all?
No, we can't remove userland interfaces.
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:[~2010-12-08 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 21:02 (Lack of) specification for RX n-tuple filtering Ben Hutchings
2010-07-22 21:50 ` Dimitris Michailidis
2010-09-07 14:43 ` Ben Hutchings
2010-12-08 16:24 ` Vladislav Zolotarov
2010-12-08 16:39 ` David Miller
2010-12-08 17:29 ` Ben Hutchings
2010-12-08 17:31 ` David Miller
2010-12-09 10:31 ` Vladislav Zolotarov
2010-12-08 17:31 ` Vladislav Zolotarov
2010-12-08 17:22 ` Ben Hutchings
2010-12-08 18:39 ` Vladislav Zolotarov
2010-12-08 19:02 ` Ben Hutchings
2010-12-08 19:10 ` Vladislav Zolotarov
2010-12-08 19:14 ` Ben Hutchings [this message]
2010-12-08 19:39 ` Ben Hutchings
2010-12-08 18:54 ` Dimitris Michailidis
2010-12-08 19:14 ` Ben Hutchings
2010-12-08 19:26 ` Dimitris Michailidis
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=1291835681.2560.53.camel@bwh-desktop \
--to=bhutchings@solarflare$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dm@chelsio$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peter.p.waskiewicz.jr@intel$(echo .)com \
--cc=vladz@broadcom$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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