From: Eric Dumazet <eric.dumazet@gmail.com>
To: Matt Carlson <mcarlson@broadcom.com>
Cc: Jesse Gross <jesse@nicira.com>,
Michael Leun <lkml20101129@newton.leun.net>,
Michael Chan <mchan@broadcom.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: Fri, 07 Jan 2011 04:04:46 +0100 [thread overview]
Message-ID: <1294369486.2704.53.camel@edumazet-laptop> (raw)
In-Reply-To: <20110107025930.GA17808@mcarlson.broadcom.com>
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 ;)
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 ?
next prev parent reply other threads:[~2011-01-07 3:04 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
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 [this message]
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=1294369486.2704.53.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=jesse@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml20101129@newton.leun.net \
--cc=mcarlson@broadcom.com \
--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