[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110107034130.GA18028@mcarlson.broadcom.com>
Date: Thu, 6 Jan 2011 19:41:30 -0800
From: "Matt Carlson" <mcarlson@...adcom.com>
To: "Eric Dumazet" <eric.dumazet@...il.com>
cc: "Matthew Carlson" <mcarlson@...adcom.com>,
"Jesse Gross" <jesse@...ira.com>,
"Michael Leun" <lkml20101129@...ton.leun.net>,
"Michael Chan" <mchan@...adcom.com>,
"David Miller" <davem@...emloft.net>,
"Ben Greear" <greearb@...delatech.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH 2.6.36] vlan: Avoid hwaccel vlan packets when vid
not used
On Thu, Jan 06, 2011 at 07:04:46PM -0800, Eric Dumazet wrote:
> Le jeudi 06 janvier 2011 ?? 18:59 -0800, Matt Carlson a ??crit :
> > On Thu, Jan 06, 2011 at 06:43:22PM -0800, Eric Dumazet wrote:
> > > Le vendredi 07 janvier 2011 ?? 03:41 +0100, Eric Dumazet a ??crit :
> > > > Le jeudi 06 janvier 2011 ?? 18:29 -0800, Matt Carlson a ??crit :
> > > >
> > > > > Hi Eric. Sorry for the delay. I was under the impression that your
> > > > > problems were software related and that you just needed a revised
> > > > > version of these VLAN patches I was sending to Michael. Is this not
> > > > > true?
> > > > >
> > > > > Having a hardware stat increment suggests this is a new problem.
> > > > > Maybe I missed it, but I didn't see what hardware you are working
> > > > > with and whether or not management firmware was enabled. Could you tell
> > > > > me that info?
> > > > >
> > > >
> > > > Hi Matt
> > > >
> > > > I started a bisection, because I couldnt sleep tonight anyway :(
> > > >
> > > > 14:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5715S
> > > > Gigabit Ethernet (rev a3)
> > > > Subsystem: Hewlett-Packard Company NC326m PCIe Dual Port Adapter
> > > > Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 43
> > > > Memory at fdff0000 (64-bit, non-prefetchable) [size=64K]
> > > > Memory at fdfe0000 (64-bit, non-prefetchable) [size=64K]
> > > > [virtual] Expansion ROM at fdbe0000 [disabled] [size=128K]
> > > > Capabilities: [40] PCI-X non-bridge device
> > > > Capabilities: [48] Power Management version 2
> > > > Capabilities: [50] Vital Product Data
> > > > Capabilities: [58] MSI: Enable+ Count=1/8 Maskable- 64bit+
> > > > Kernel driver in use: tg3
> > > > Kernel modules: tg3
> > > >
> > > >
> > >
> > > $ ethtool -i eth2
> > > driver: tg3
> > > version: 3.115
> > > firmware-version: 5715s-v3.28
> > > bus-info: 0000:14:04.0
> > > $ dmesg | grep ASF
> > > [ 6.220577] tg3 0000:14:04.0: eth2: RXcsums[1] LinkChgREG[0] MIirq[0]
> > > ASF[0] TSOcap[1]
> > > [ 6.228586] tg3 0000:14:04.1: eth3: RXcsums[1] LinkChgREG[0] MIirq[0]
> > > ASF[0] TSOcap[1]
> >
> > Thanks. So management firmware is disabled. This should be
> > straightforward case.
> >
> > I'm wondering if I'm misunderstanding something though. You said earlier
> > that VLAN tagging doesn't work unless you applied my patch. Is this no
> > longer true?
> >
>
> I dont apply your patch because Jesse said it was not a good patch ;)
Oh.
> Maybe I missed something and it must be applied ? Problem is : current
> Linus tree now includes net-next-2.6 and vlan doesnt work. You should
> resubmit it perhaps ?
Yes, something needs to be submitted. I want to make sure we aren't
chasing the same problem though. If the patch(es) fix your problem,
then I can concentrate on finalizing the patch.
I can combine my last patch (the one that always enabled VLAN tag
stripping) and the previous patch (that implements all your comments so
far) into one patch, but that still leaves the behavior Michael noted
unaddressed.
Michael, did you ever find out whether or not RXD_FLAG_VLAN was being
set?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists