netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: netdev@oss.sgi.com
Subject: Re: network interface cards native vlans support in linux kernel?
Date: Wed, 22 Oct 2003 10:01:49 -0700	[thread overview]
Message-ID: <3F96B7FD.7080607@candelatech.com> (raw)
In-Reply-To: <20031022140624.A9145@vip.cybercity.dk>

Rask Ingemann Lambertsen wrote:
> On Wed, Jul 09, 2003 at 11:28:15AM -0400, Jeff Garzik wrote:
> 
>>On Wed, Jul 09, 2003 at 06:19:51PM +0300, Andrius Kasparavicius wrote:
>>
>>>hello, as far as i know, currently there is no native vlan support in
>>>network device drivers. I mean, always need patching MTU.. add 4 bytes..
>>>
>>>is there any problems to include full vlans support?
>>
>>Native VLAN support has been in the kernel for a while.
>>
>>A few drivers still need patching, and unfortunately the VLAN driver
>>patches floating around all need cleaning up.
> 
> 
> What does a driver need to do to make sure it can handle vlan frames? Is it
> enought to be prepared to handle frames of size dev->mtu+4? How do I know 4
> bytes will be enough tomorrow when someone introduces VLAN2 with a 64-bit tag?
> Checking for CONFIG_VLAN is of no use, right?

It needs to be able to handle 1518 bytes (+crc), send and receive.  I'd
suggest using the Intel e100 or e1000, as they both support VLANs just fine.
Most other GigE nics work too.

Apply the patches in the VLAN howto if you need another NIC that needs
patching.  There seems to be zero motivation by 100bt driver authors to
add VLAN support to the drivers that still need it...

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2003-10-22 17:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 15:19 network interface cards native vlans support in linux kernel? Andrius Kasparavicius
2003-07-09 15:28 ` Jeff Garzik
2003-09-11 14:57   ` Rask Ingemann Lambertsen
2003-10-22 12:06   ` Rask Ingemann Lambertsen
2003-10-22 17:01     ` Ben Greear [this message]
2003-11-12 19:48       ` Rask Ingemann Lambertsen
2003-07-09 17:15 ` Ben Greear
2003-07-09 19:12   ` Andrius Kasparavicius
2003-07-11 14:59   ` Andrius Kasparavicius
2003-07-11 17:11     ` Ben Greear
2003-07-11 17:18       ` Jeff Garzik
2003-07-11 17:25         ` Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2003-07-09 15:33 Hen, Shmulik
2003-07-09 17:13 ` Ben Greear

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=3F96B7FD.7080607@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=netdev@oss.sgi.com \
    --cc=rask@sygehus.dk \
    /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;
as well as URLs for NNTP newsgroup(s).