Date: Sat, 24 Aug 2013 16:42:30 +0400 From: "Alexander V. Chernikov" <melifaro@ipfw.ru> To: Adrian Chadd <adrian@freebsd.org> Cc: FreeBSD Net <freebsd-net@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: [rfc] migrate lagg to an rmlock Message-ID: <5218AA36.1080807@ipfw.ru> In-Reply-To: <CAJ-Vmo=VKVDEmmPrTbob6Ft%2B7FWypodNoL36Og=7p_CXBSfktg@mail.gmail.com> References: <CAJ-Vmo=VKVDEmmPrTbob6Ft%2B7FWypodNoL36Og=7p_CXBSfktg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net To > unsubscribe, send any mail to > "freebsd-net-unsubscribe@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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5218AA36.1080807>