Date: Tue, 07 Oct 2003 13:44:13 -0300 From: "Daniel C. Sobral" <dcs@tcoip.com.br> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: net@freebsd.org Subject: Re: adding if_dev member to struct ifnet Message-ID: <3F82ED5D.3060803@tcoip.com.br> In-Reply-To: <20030930182359.GD31908@Odin.AC.HMC.Edu> References: <20030930171535.GA31908@Odin.AC.HMC.Edu> <13247.1064944601@critter.freebsd.dk> <20030930182359.GD31908@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote: > > Not today, since none of them get used in the paths that do this. In > general the network code doesn't care what you call an interface. There > are a few corners where it does, but nothing that isn't specific to > a certain set of drivers. Additionally, it is necessary to not have > members called if_name and if_unit if we have if_xname as the primary > driver name. It's also worth noting that one of the things I want to do > is break the driver+unit mapping for certain types of pseudo devices. > Specifically vlan devices should be allocatable by creating an interface > with a name like fxp0.100 so while you could synthesize a unit number, > it wouldn't have any useful meaning. I wonder how that works for vlans over bridges... -- Daniel C. Sobral Gerência de Operações Divisão de Comunicação de Dados Coordenação de Segurança VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F82ED5D.3060803>