Re: [rfc] migrate lagg to an rmlock

From: Alexander V. Chernikov <melifaro_at_ipfw.ru>
Date: Sat, 24 Aug 2013 16:42:30 +0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24.08.2013 00:54, Adrian Chadd wrote:
> Hi,
> 
> I'd like to commit this to -10. It migrates the if_lagg locking
> from a rw lock to a rm lock. We see a bit of contention between the
> transmit and
We're running lagg with rmlock on several hundred heavily loaded
machines, it really works better.
However, there should not be any contention between receive and
transmit side since there is actually no _real_ need to lock RX (and
even use lagg receive code at all):

http://lists.freebsd.org/pipermail/svn-src-all/2013-April/067570.html

> receive sides of lagg during traffic loads (10+ gigabit per
> second.) Using rmlocks eliminate this.
> 
> http://people.freebsd.org/~adrian/netflix/20130819-lagg-rmlock-1.diff
>
>  Thanks,
> 
> 
> -adrian _______________________________________________ 
> freebsd-net_at_freebsd.org mailing list 
> http://lists.freebsd.org/mailman/listinfo/freebsd-net To
> unsubscribe, send any mail to
> "freebsd-net-unsubscribe_at_freebsd.org"
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlIYqjYACgkQwcJ4iSZ1q2n9fgCePHOfC3tzBIG54ayNg7d8TKMC
gIMAn2/paUBpDIRVd+3s7snNFCmZNWgd
=i6Ye
-----END PGP SIGNATURE-----
Received on Sat Aug 24 2013 - 10:43:43 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:40 UTC