Date: Tue, 17 Nov 2015 09:20:14 -0700 From: Alan Somers <asomers@freebsd.org> To: Kurt Jaeger <lists@opsec.eu> Cc: Johan Hendriks <joh.hendriks@gmail.com>, FreeBSD <freebsd-stable@freebsd.org> Subject: Re: LACP with 3 interfaces. Message-ID: <CAOtMX2jGg8w2SxgUnYt9rTd8uEHm21OgYQ5hfDmuCn8wb=6iDA@mail.gmail.com> In-Reply-To: <20151117161627.GH35480@home.opsec.eu> References: <564B4736.3000100@gmail.com> <CAOtMX2gghJMabmYbPze8%2Bm4okPViixtgWCW0aR6CSON45f_05A@mail.gmail.com> <20151117161627.GH35480@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 17, 2015 at 9:16 AM, Kurt Jaeger <lists@opsec.eu> wrote: > Hi! > >> > Is there something we can do to make sure lagg0 uses all the interfaces. >> >> Nope. LACP doesn't actively load balance its interfaces. > > On FreeBSD 11 > > man lagg(4) > > says: > > The driver currently supports the aggregation protocols failover (the > default), lacp, loadbalance, roundrobin, broadcast, and none. > > with > > roundrobin Distributes outgoing traffic using a round-robin scheduler > through all active ports and accepts incoming traffic from > any active port. > > If the three ports are needed for sending, shouldn't this work ? > Be careful with roundrobin or loadbalance. Both of them will distribute outbound traffic across all ports, but at the expense of causing your NFS clients to receive out-of-order TCP packets. This increases their CPU load. You may find that performance with roundrobin is actually worse than with LACP because of the out-of-order issue. Also, neither roundrobin nor loadbalance will help distribute inbound traffic. -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2jGg8w2SxgUnYt9rTd8uEHm21OgYQ5hfDmuCn8wb=6iDA>