From: Alexander Duyck <alexander.h.duyck@intel•com>
To: Ben Hutchings <bhutchings@solarflare•com>
Cc: zhou rui <zhourui.cn@gmail•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"e1000-devel@lists•sourceforge.net"
<e1000-devel@lists•sourceforge.net>
Subject: Re: how to set vlan filter for intel 82599
Date: Tue, 26 Apr 2011 08:22:55 -0700 [thread overview]
Message-ID: <4DB6E34F.5000203@intel.com> (raw)
In-Reply-To: <1303824705.3032.359.camel@localhost>
On 4/26/2011 6:31 AM, Ben Hutchings wrote:
> On Tue, 2011-04-26 at 12:39 +0800, zhou rui wrote:
> [...]
>> i set the filter like below:
>>
>> for a vlanid=50, it always match the last rule (action 7)
>>
>> ./ethtool -K eth5 ntuple off
>> ./ethtool -K eth5 ntuple on
>> ./ethtool -U eth5 flow-type tcp4 vlan 32 vlan-mask 0xF01F action 1
>> ./ethtool -U eth5 flow-type udp4 vlan 32 vlan-mask 0xF01F action 1
>> ./ethtool -U eth5 flow-type udp4 vlan 64 vlan-mask 0xF01F action 7
>> ./ethtool -U eth5 flow-type tcp4 vlan 64 vlan-mask 0xF01F action 7
>>
>> I tried the latest ixgbe driver 3.3.9, it reports:
>>
>> Cannot add new RX n-tuple filter: Operation not permitted
>>
>> ./ethtool -V
>> ethtool version 2.6.36
>
> Check dmesg; there should be an error message there. Of course the
> error code should be EINVAL and not EPERM.
>
> Ben.
>
The problem is likely the vlan-mask. The only valid VLAN masks
supported are 0xFFFF, 0x0FFF, 0xF000, and 0x0000. The hardware cannot
partially mask either the priority nor the VLAN TCI.
Thanks,
Alex
next prev parent reply other threads:[~2011-04-26 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 2:19 how to set vlan filter for intel 82599 zhou rui
2011-04-26 2:57 ` Ben Hutchings
2011-04-26 3:39 ` zhou rui
2011-04-26 3:51 ` Ben Hutchings
2011-04-26 4:39 ` zhou rui
2011-04-26 13:31 ` Ben Hutchings
2011-04-26 15:22 ` Alexander Duyck [this message]
2011-04-26 15:30 ` zhou rui
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=4DB6E34F.5000203@intel.com \
--to=alexander.h.duyck@intel$(echo .)com \
--cc=bhutchings@solarflare$(echo .)com \
--cc=e1000-devel@lists$(echo .)sourceforge.net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=zhourui.cn@gmail$(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