Date: Wed, 21 Dec 2011 13:22:02 +0100 From: Stefan Bethke <stb@lassitu.de> To: Adrian Chadd <adrian@freebsd.org> Cc: Oleksandr Tymoshenko <gonzo@freebsd.org>, "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org> Subject: Re: Updated switch/glue patch? Message-ID: <BD36B2D3-E827-4B2B-9CBF-1E43C0B6121B@lassitu.de> In-Reply-To: <CAJ-Vmo=ERixAN96QSOaaej8avPHYkGC28AJZErdEhO0%2B=1R0Pw@mail.gmail.com> References: <CAJ-Vmon8%2BOXQ4g752zZEB-O0BR0sFWO0QUvw--xp2jsBDkx6tQ@mail.gmail.com> <0F6CC18F-6973-42A2-AC03-F01BF59458AE@lassitu.de> <CAJ-Vmo=Y8pp4iFnw%2B1hcPae6QXFboz=a7puwgC1kVSZ3JwMgPQ@mail.gmail.com> <1100F70E-9DA9-4163-AC9A-423ECE5AA9A3@lassitu.de> <CAJ-VmonrnJ7cC6u2LsL9AGusz_%2BkSwY62Rr1__sg5U_NynJ1SQ@mail.gmail.com> <CAJ-Vmo=WSN1oLM=B2HqSHrWyOaOD9BSwwu8=1Wys0CLRJ_N-TA@mail.gmail.com> <C637C171-A1A2-4296-84FA-6DE97137DC42@lassitu.de> <CAJ-Vmon2boy7OCh_4O0MeCi0yCdZu0OYb5dxHCEK=-%2B46zBGtg@mail.gmail.com> <CAJ-Vmoku5eLEYi5_DXVxK=0=4Ewn2aGepv3YUw4ApuVh_7y2%2Bw@mail.gmail.com> <CAJ-VmonvpnaS1rAO%2BsDRh1E5WfsrZTYE297Kc96prhfKjrM89Q@mail.gmail.com> <CAJ-VmokQxQs2DUKL=ONyxnnS7Q28ytmwZJ_thqvc4SvMkmS=cQ@mail.gmail.com> <18CABB46-9B9A-41CB-8742-6723C5FF4D67@lassitu.de> <C0BF20FD-E30F-4E9C-A0FE-500BE4807B99@bsdimp.com> <CAJ-VmokgiQCEG4et3X=3o_MuCMkO9MqkKqa-fjdpEqQNucn=Lw@mail.gmail.com> <2CBD8651-E132-49DC-A082-37A8F5C626EA@bsdimp.com> <CAJ-VmomySBQeMqr8meQDpSLBC1%2By_%2BvMQsSt9OWFaCA67O8G=w@mail .gmail.com> <AFE755D6-E462-40B4-A97B-9261303B3A4F@lassitu.de> <CAJ-Vmo=ERixAN96QSOaaej8avPHYkGC28AJZErdEhO0%2B=1R0Pw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 20.12.2011 um 16:25 schrieb Adrian Chadd: > Hm, and I also need to see whether it's worthwhile keeping the > vlangroup config method, or whether the ar8216/ar8316 (and the others > supported in zrouter) really want to support a set of VLANs per port. > The AR8316 datasheet describes how it works - there's a table of known > VLANs and a bitmap in each VLAN entry describing which ports are able > to be used. There's also a way to configure port isolation, and the > ingres/egres port is configured by a magic 2 byte header added to each > ethernet frame. You're describing it as if it were different from the RTL8366RB. I'm open to replace "vlangroup" with a better term. I picked it to = distinguish it from ifconfig's use of "vlan" to configure the .1q VLAN = ID (VID). In the switch chips, as you correctly explain, there is a = VLAN configuration table (usually 16 entries), where each entry has the = VID, the member ports and potentially a number of additional parameters = (PCP, etc.) This entry I'm calling "vlangroup" (that's what the = datasheet for the RTL8306S calls it). I'd be happy if we could find a = better term. The Linux switch api ignores the VLAN configuration table and presents = the switch as if you had an entry for each possible VID. It's slightly = more complicated in the switch driver, but we could go down the same = route. Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BD36B2D3-E827-4B2B-9CBF-1E43C0B6121B>