From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Date: Mon, 26 Jul 2004 20:18:07 +0000 Subject: Re: [PATCH] Limit number of concurrent hotplug processes Message-Id: <20040726131807.47816576.akpm@osdl.org> List-Id: References: <40FD23A8.6090409@suse.de> <20040725182006.6c6a36df.akpm@osdl.org> <4104E421.8080700@suse.de> In-Reply-To: <4104E421.8080700@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Hannes Reinecke Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Hannes Reinecke wrote: > > > > >> Any comments/suggestions welcome; otherwise please apply. > > > > > > I suggest you just use a semaphore, initialised to a suitable value: > > > > > > static struct semaphore foo = __SEMAPHORE_INITIALIZER(foo, 50); > > > > > > { > > ... > > down(&foo); > > ... > > up(&foo); > > ... > > } > > > Hmm; looks good, but: It's not possible to reliably change the maximum > number of processes on the fly. > > The trivial way of course it when the waitqueue is empty and no > processes are holding the semaphore. But it's quite non-obvious how this > should work if processes are already holding the semaphore. > We would need to wait for those processes to finish, setting the length > of the queue to 0 (to disallow any other process from grabbing the > semaphore), and atomically set the queue length to the new value. > Apart from the fact that we would need a worker thread for that > (otherwise the calling process might block indefinitely), there is no > guarantee that the queue ever will become empty, as hotplug processes > might be generated at any time. > > Or is there an easier way? Well if you want to increase the maximum number by ten you do: for (i = 0; i < 10; i++) up(&foo); and similarly for decreasing the limit. That will involve doing down()s, which will automatically wait for the current number of threads to fall to the desired level. But I don't really see a need to tune this on the fly - probably the worse problem occurs during bootup when the operator cannot perform tuning. So a __setup parameter seems to be the best way of providing tunability. Initialise the semaphore in usermodehelper_init(). ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id040&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel