On Fri, May 08, 2009 at 11:41:17PM +0200, Ed Schouten wrote: > Hi, > > * vasanth raonaik <vasanth.raon...@gmail.com> wrote: > > Hello Jt, > > > > I am a newbee in this alias. I am having a very basic question. It would 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. > > 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?
pgpy3bE29OnYg.pgp
Description: PGP signature
