From: "Matt Carlson" <mcarlson@broadcom.com>
To: "Jesse Gross" <jesse@nicira.com>
Cc: "Michael Leun" <lkml20101129@newton.leun.net>,
"Matthew Carlson" <mcarlson@broadcom.com>,
"Michael Chan" <mchan@broadcom.com>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
"David Miller" <davem@davemloft.net>,
"Ben Greear" <greearb@candelatech.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 2.6.36] vlan: Avoid hwaccel vlan packets when vid not used
Date: Thu, 6 Jan 2011 19:24:59 -0800 [thread overview]
Message-ID: <20110107032459.GA17959@mcarlson.broadcom.com> (raw)
In-Reply-To: <AANLkTi=hGRW+DwoKQzxPAZao6-y_tvn6nNXS-tj_-Y6T@mail.gmail.com>
On Sat, Dec 18, 2010 at 07:38:00PM -0800, Jesse Gross wrote:
> On Tue, Dec 14, 2010 at 11:16 PM, Michael Leun
> <lkml20101129@newton.leun.net> wrote:
> > OK - all tests done on that DL320G5:
> >
> > For completeness, 2.6.37-rc5 unpatched:
> >
> > eth0, no vlan configured: totally broken - see double tagged vlans
> > without tag, single or untagged packets missing at all
>
> Random behavior? This one is somewhat hard to explain - maybe there
> are some other factors. eth0 has ASF on, so it always strips tags. I
> would expect it to behave like the vlan configured case.
>
> >
> > eth0, vlan configured: see packets without vlan tag (see double tagged
> > packets with one vlan tag)
>
> Both ASF and vlan group configured cause tag stripping to be enabled.
> Missing tag.
>
> >
> > eth1 same as originally reported:
> > without vlan configured see vlan tags (single and double tagged as
> > expected)
>
> No ASF and no vlan group means tag stripping is disabled. Have tag.
>
> > with vlan configured: see packets without vlan tag (see double tagged
> > packets with one vlan tag)
>
> Configuring vlan group causes stripping to be enabled. Missing tag.
>
> >
> >
> > 2.6.37-rc5, your tg3 use new vlan-code patch:
> >
> > eth0, no vlan configured: ?see packets without vlan tag (see double
> > tagged packets with one vlan tag)
>
> ASF enables tag stripping. Missing tag.
>
> > eth1, no vlan configured: see vlan tags (single and double tagged as
> > expected)
>
> No ASF, no vlan group means no stripping. Have tag.
>
> >
> >
> > eth0, vlan configured: as without vlan
>
> ASF enables stripping. Missing tag.
>
> > eth1, vlan configured: as without vlan
>
> With this patch vlan stripping is only enabled when ASF is on, so no
> stripping. Have tag.
>
> >
> > 2.6.37-rc5, your tg3 use new vlan-code patch with test patch ontop
> >
> > eth1 no vlan configured: see packets without vlan tag (see double tagged
> > packets with one vlan tag)
>
> With the second patch, vlan stripping is always enabled. Missing tag.
>
> > eth1 with vlan: the same
>
> Stripping still always enabled. Missing tag.
>
> The bottom line is whenever vlan stripping is enabled we're missing
> the outer tag. It might be worth adding some debugging in the area
> before napi_gro_receive/vlan_gro_receive (depending on version). My
> guess is that (desc->type_flags & RXD_FLAG_VLAN) is false even for
> vlan packets on this NIC.
>
> You said that everything works on the 5752? Matt, is it possible that
> the 5714 either has a problem with vlan stripping or a different way
> of reporting it?
I don't think this is a 5714 specific issue. I think the problem is
rooted in the fact that the VLAN tag stripping is enabled.
Your RXD_FLAG_VLAN idea sounds unlikely to me, but it's worth a check.
The patch here is using __vlan_hwaccel_put_tag(), which informs the
stack a VLAN tag is present. If this is indeed a reporting problem, I'm
not sure what else the driver should be doing.
> Also, why does ASF require vlan stripping?
This is a firmware limitation.
next prev parent reply other threads:[~2011-01-07 3:25 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 19:17 2.6.35 -> 2.6.36 panic when vlan and promisc with tg3 Michael Leun
2010-11-30 0:19 ` Ben Greear
2010-11-30 3:10 ` Jesse Gross
2010-11-30 3:26 ` David Miller
2010-11-30 8:59 ` Michael Leun
2010-11-30 9:20 ` Eric Dumazet
2010-11-30 22:27 ` Jesse Gross
2010-12-01 10:17 ` Michael Leun
2010-12-01 10:55 ` [PATCH 2.6.36] vlan: Avoid hwaccel vlan packets when vid not used Eric Dumazet
2010-12-05 2:07 ` Michael Leun
2010-12-05 8:03 ` Eric Dumazet
2010-12-05 9:55 ` Michael Leun
[not found] ` <20101205114404.7c0cddc2@xenia.leun.net>
[not found] ` <AANLkTikrDTCDxsyOG4m0XcrOY=3pTRwWqnPGsio9cBFj@mail.gmail.com>
2010-12-06 19:34 ` Michael Leun
2010-12-06 20:04 ` Jesse Gross
2010-12-06 21:27 ` Michael Leun
2010-12-13 0:11 ` Jesse Gross
2010-12-13 22:45 ` Matt Carlson
2010-12-14 4:07 ` Jesse Gross
2010-12-14 19:15 ` Matt Carlson
2010-12-14 21:46 ` Jesse Gross
2010-12-15 0:24 ` Michael Leun
2010-12-15 1:34 ` Matt Carlson
2010-12-15 7:16 ` Michael Leun
2010-12-19 3:38 ` Jesse Gross
2011-01-07 3:24 ` Matt Carlson [this message]
2011-01-07 4:36 ` Jesse Gross
2011-01-13 1:21 ` Matt Carlson
2011-01-13 15:06 ` Jesse Gross
2011-01-13 20:50 ` Matt Carlson
2011-01-13 21:58 ` Jesse Gross
2011-01-14 1:15 ` Matt Carlson
2011-01-14 17:49 ` Jesse Gross
2011-01-14 18:38 ` Matt Carlson
2011-01-19 16:15 ` Jesse Gross
2011-01-01 17:03 ` Eric Dumazet
2011-01-02 0:27 ` Jesse Gross
2011-01-02 16:05 ` Eric Dumazet
2011-01-06 21:01 ` Jesse Gross
2011-01-06 23:34 ` Eric Dumazet
2011-01-07 1:20 ` Eric Dumazet
2011-01-07 2:29 ` Matt Carlson
2011-01-07 2:41 ` Eric Dumazet
2011-01-07 2:43 ` Eric Dumazet
2011-01-07 2:59 ` Matt Carlson
2011-01-07 3:04 ` Eric Dumazet
2011-01-07 3:41 ` Matt Carlson
2011-01-07 3:54 ` Eric Dumazet
2011-01-07 4:38 ` Jesse Gross
2010-12-08 16:47 ` David Miller
2010-12-08 23:06 ` [stable] " Greg KH
2010-12-08 23:16 ` Greg KH
2010-12-09 1:25 ` Eric Dumazet
2010-12-09 20:13 ` Greg KH
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=20110107032459.GA17959@mcarlson.broadcom.com \
--to=mcarlson@broadcom.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=greearb@candelatech.com \
--cc=jesse@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml20101129@newton.leun.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.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