Date: Sat, 9 May 2009 13:35:00 +0200 From: Lars Engels <lars.engels@0x20.net> To: Ed Schouten <ed@80386.nl> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, jt@0xabadba.be, vasanth raonaik <vasanth.raonaik@gmail.com> Subject: Re: concurrent sysctl implementation Message-ID: <20090509113459.GD56667@e.0x20.net> In-Reply-To: <20090508214117.GY58540@hoeg.nl> References: <a0806f900905050107u4cbf0624oc83aafa54ae651f0@mail.gmail.com> <d9f479c10905050239u5d6d8304y1f63e41eabee8624@mail.gmail.com> <20090508214117.GY58540@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--i7F3eY7HS/tUJxUd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 08, 2009 at 11:41:17PM +0200, Ed Schouten wrote: > Hi, >=20 > * vasanth raonaik <vasanth.raonaik@gmail.com> wrote: > > Hello Jt, > >=20 > > I am a newbee in this alias. I am having a very basic question. It woul= d be > > really good if you could give me some of this information. > > Could you please elaborate on what is the current architecture of sysctl > > implementation and How the concurrency would benefit us. >=20 > Right now sysctl is synchronized using the sysctl lock. The problem is > that certain sysctls just block for a very long time (especially some of > the GEOM ones). We also call sysctl when we execute new processes, to > obtain a random number for the stack protector. This means we have quite > a lot of contention on it. This lock needs to be there, because sysctls > can be added and removed on demand. Why is sysctl used to get a random number? Can't we get a different source for it? --i7F3eY7HS/tUJxUd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkoFamMACgkQKc512sD3afgmLACfY9bwMdM+B8qWEvDPm2oEaaGe mxUAn3YSBnxkrHOkm+BSCBBdhP2PRQIw =mlf8 -----END PGP SIGNATURE----- --i7F3eY7HS/tUJxUd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090509113459.GD56667>