Date: Thu, 27 Nov 2008 11:28:05 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-net@freebsd.org Subject: Re: TSO on VLAN interface, FreeBSD 7 Message-ID: <gglsni$ab$1@ger.gmane.org> In-Reply-To: <20081127100758.0000577c@unknown> References: <20def4870811260540x3d44a02bw43b6d18bc675de67@mail.gmail.com> <20def4870811260541x2f9bb410o44152a406407686@mail.gmail.com> <20081127100758.0000577c@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Gergely CZUCZY wrote: > Hello, > > I'd be also pretty interested in this one. And also, the question > arises me for the very same issue, for LACP interfaces, and > VLAN-over-LACP interfaces (lagg(4) as LACP). > Having a gateway requires performances, and it often also means having > VLANs, and LACP for failure tolerance. So I think this is a pretty > important issue. > > On Wed, 26 Nov 2008 15:41:09 +0200 > "Yony Yossef" <yonyossef.lists@gmail.com> wrote: > >> Hi All, >> >> When I create a VLAN interface it does not inherit the parent >> interface capabilities. >> Is there a way to enable TSO (as other capabilities) on VLAN >> interfaces? It will probably be implemented in the future: http://lists.freebsd.org/pipermail/freebsd-net/2008-October/019729.html [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJLnY1ldnAQVacBcgRAgrJAKCIJ8+hj4oMizflHAD5J3W22Spr6ACg0kCw MjE+lpNwwJC54g852p/r7Fc= =hclj -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gglsni$ab$1>