mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Ben Greear <greearb@candelatech.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"David S. Miller" <davem@redhat.com>,
	<linux-kernel@vger.kernel.org>, <netdev@oss.sgi.com>
Subject: Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission
Date: Sun, 7 Jan 2001 13:53:48 -0500 (EST)	[thread overview]
Message-ID: <Pine.GSO.4.30.0101071344020.18916-100000@shell.cyberus.ca> (raw)
In-Reply-To: <3A58C57A.131BFEF2@candelatech.com>



On Sun, 7 Jan 2001, Ben Greear wrote:
> jamal wrote:
> >
> > erm, this is a MUST. You MUST factor the hardware VLANs and be totaly
> > 802.1q compliant. Also of interest is 802.1P and D. We must have full
> > compliance, not some toy emulation.
>
> I have seen neither hardware nor spec sheets on how these NICs are doing
> VLAN 'support'.  So, I don't know what the best way to support them is.
>

Most of the GIGe interfaces do provide VLAN insertion/removal. You
pass/receive it as part of the DMA descriptor.

> If it requires driver changes, then the ethernet driver folks will need
> to be involved.
>

I think the design MUST consider not just a poor man's VLAN way of
doing things. You and the other VLAN folks (Gleb and co) will have to iron
that out. Basically, all i am saying is that if there is going to be a
linux solution at some point, the requirement for these devices is a MUST.
Please involve me in discussions you guys end up having.

> There is also a difference between supporting hardware VLAN solutions
> and being 100% compliant:  If I can send/receive packets that are
> 100% compliant from an RTL 8139 NIC, then as far as the world (ie Switch) knows,
> I am 100% compliant.
>

ok.

> If the specific VLAN hardware features are not supported in some exotic
> NIC, then that should just mean slightly less performance, or worst cast,
> not supporting that particular NIC.

The included design must be flexible enough to allow for this. As much as
i hate it, some vendors will continue releasing binaries only for their
code.

>
> My vlan code supports setting of Priority bits already (thats' the .1P, right?)
>

right. There's a lot of work to be done in that area.

> What is the .1D stuff about?
>

spanning tree. Seems the bridging code already does this.

cheers,
jamal

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-07 18:55 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08  8:12 [PATCH] hashed device lookup (New Benchmarks) Ben Greear
2001-01-06 21:33 ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!) Ben Greear
2001-01-06 23:17   ` David S. Miller
2001-01-07  4:06     ` Ben Greear
2001-01-07 13:42       ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission Alan Cox
2001-01-07 15:33         ` Matti Aarnio
2001-01-07 16:46           ` Alan Cox
2001-01-07 17:32             ` Matti Aarnio
2001-01-07 19:02         ` Ben Greear
2001-01-07 18:06           ` Alan Cox
2001-01-07 18:53             ` Matti Aarnio
2001-01-07 19:30             ` Ben Greear
2001-01-07 18:30               ` Alan Cox
2001-01-07 22:40             ` 5116
2001-01-08  2:19             ` David Ford
2001-01-09 20:25             ` Christopher E. Brown
2001-01-10  2:47               ` Ben Greear
2001-01-07 18:21           ` jamal
2001-01-07 19:00             ` Matti Aarnio
2001-01-07 19:10               ` jamal
2001-01-07 19:24                 ` Matti Aarnio
2001-01-08  0:21                   ` jamal
2001-01-07 19:37             ` Ben Greear
2001-01-07 18:53               ` jamal [this message]
2001-01-07  5:36     ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!) David S. Miller
2001-01-07  3:29   ` Chris Wedgwood
2001-01-07  6:15     ` Ben Greear
2001-01-07 10:22     ` David Ford
2001-01-07 12:01       ` David S. Miller
2001-01-08  5:32         ` Andi Kleen
2001-01-08  6:12           ` Chris Wedgwood
2001-01-08  6:26             ` Andi Kleen
2001-01-08  6:57               ` David Ford
2001-01-08 13:08                 ` jamal
2001-01-09 13:28                   ` Blu3Viper
2001-01-08  6:13           ` Blu3Viper
2001-01-07 12:13       ` Chris Wedgwood
2001-01-07 12:19         ` David Ford
2001-01-07 16:56     ` jamal
2001-01-07 17:37       ` Gleb Natapov
2001-01-07 18:02         ` routable interfaces WAS( " jamal
2001-01-07 19:21           ` routable interfaces WAS( Re: [PATCH] hashed device lookup (DoesNOT " Ben Greear
2001-01-07 18:29             ` jamal
2001-01-07 18:51               ` Gleb Natapov
2001-01-07 19:05                 ` jamal
2001-01-07 19:19               ` routable interfaces WAS( Re: [PATCH] hashed device lookup(DoesNOT " Sandy Harris
2001-01-07 20:42                 ` Ben Greear
2001-01-08  0:37                   ` jamal
2001-01-08  5:25                     ` routable interfaces WAS( Re: [PATCH] hashed device lookup(DoesNOTmeet " Ben Greear
2001-01-08 13:05                       ` jamal
2001-01-07  3:29   ` [PATCH] hashed device lookup (Does NOT meet " Andi Kleen
2001-01-07  4:00     ` jamal
2001-01-07  4:06       ` Andi Kleen
2001-01-07  5:43       ` David S. Miller
2001-01-07 11:40         ` [little bit OT] ip _IS_ _NOT_ ifconfig and route ! (was Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!)) Henning P. Schmiedehausen
2001-01-07 11:50         ` David S. Miller
2001-01-07 13:47         ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission Alan Cox
2001-01-07 16:12           ` jamal
2001-01-07 16:51             ` Alan Cox
2001-01-07 15:56         ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!) jamal
2001-01-07 16:30           ` Gleb Natapov
2001-01-07 16:36             ` jamal
2001-01-07 19:54           ` [PATCH] hashed device lookup (Does NOT meet Linus' sumissionpolicy!) Ben Greear
2001-01-07  6:24       ` Ben Greear
2001-01-07  5:29         ` Andi Kleen
2001-01-07  6:22     ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!) Ben Greear
2001-01-07  5:27       ` Andi Kleen
2001-01-07  8:11         ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!) (Benchmarks) Ben Greear
2001-01-07  7:15           ` Andi Kleen
2001-01-08  7:00           ` [PATCH] hashed device lookup (New Benchmarks) David S. Miller
2001-01-08 16:26             ` Ben Greear
2001-01-08 16:50               ` Andi Kleen
2001-01-09 16:27                 ` Ben Greear
2001-01-07 13:50       ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission Alan Cox
2001-01-07 16:44         ` Miquel van Smoorenburg
2001-01-07 19:09         ` Ben Greear
2001-01-07  5:40   ` [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!) David S. Miller

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=Pine.GSO.4.30.0101071344020.18916-100000@shell.cyberus.ca \
    --to=hadi@cyberus.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®