lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20150220010352.GA300@roeck-us.net> Date: Thu, 19 Feb 2015 17:03:52 -0800 From: Guenter Roeck <linux@...ck-us.net> To: roopa <roopa@...ulusnetworks.com> Cc: Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org, davem@...emloft.net, vivien.didelot@...oirfairelinux.com, jerome.oufella@...oirfairelinux.com, andrew@...n.ch, cphealy@...il.com Subject: Re: [PATCH RFC 2/2] net: dsa: bcm_sf2: implement HW bridging operations On Thu, Feb 19, 2015 at 04:51:30PM -0800, roopa wrote: > > > >Not sure yet what to do about setting the fdb aging time. I don't see a > >mechanism to do that. No idea how important that is. > rocker, the only consumer today relies on the bridge driver aging of learnt > entries. > You could do the same. > Remember that we are dealing with hardware switch chips. Those chips won't time out fdb entries just because the kernel's bridge driver thinks that it should. Am I missing something ? Guenter -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists