From: Evan Bigall <evan.bigall@scalent.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Nate Carlson <natecars@natecarlson.com>
Subject: Re: Problem with VLANs on tg3 NICs
Date: Fri, 19 Jan 2007 08:09:18 -0500 [thread overview]
Message-ID: <45B0C2FE.9050009@scalent.com> (raw)
In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E04F1BF@liverpoolst.ad.cl.cam.ac.uk>
>If its broadcasting all VLAN-tagged traffic to all ports that's
>disastrous for performance. You'd be much better off setting up a
>separate bridge for each VLAN. Alternatively, it might be worth looking
>at The Linux Switching Appliance (LISA) project -- their bridge supports
>VLAN trunks.
>
>
I'd have to do a tcpdump to be sure but empirically I haven't noticed
any performance problems (and these are nfs booted images).
All I'm expecting of the bridge code is that it ignore the tag and
deliver the packet by mac address as normal. Because all this works with
other than the tg3 driver I'm confident the bridge code is doing what I
expect. The problem is not with the bridge, the problem is with the tg3
driver. I believe that any network utility on top of the tg3 driver
would have the same problem, as the tg3 driver is stripping the vlan
tags before it passes them on.
Evan
next prev parent reply other threads:[~2007-01-19 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 19:33 Problem with VLANs on tg3 NICs Evan Bigall
2007-01-18 20:37 ` Ian Pratt
2007-01-18 21:46 ` Evan Bigall
2007-01-18 22:35 ` Ian Pratt
2007-01-19 0:30 ` Evan Bigall
2007-01-19 6:04 ` Nate Carlson
2007-01-19 7:52 ` Ian Pratt
2007-01-19 13:09 ` Evan Bigall [this message]
2007-01-19 14:14 ` Ian Pratt
2007-01-19 14:17 ` Christopher G. Stach II
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=45B0C2FE.9050009@scalent.com \
--to=evan.bigall@scalent.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=natecars@natecarlson.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.