From: Andrew Morton <akpm@osdl.org>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Limit number of concurrent hotplug processes
Date: Tue, 27 Jul 2004 07:24:09 +0000 [thread overview]
Message-ID: <20040727002409.68d49d7c.akpm@osdl.org> (raw)
In-Reply-To: <4105FE68.7040506@suse.de>
Hannes Reinecke <hare@suse.de> wrote:
>
> The problem (from my point of view) with semaphores is that we don't
> have an direct counter of the number of processes waiting on that
> semaphore to become free. We do have a counter for the number of
> processes which are allowed to use the semaphore concurrently (namely
> ->count), but the number of waiting processes must be gathered
> indirectly by the number of entries in the waitqueue.
Well one could add the number of sleepers to the semaphore, or write some
function which counts the number of entries on the waitqueue or something.
But the result of this query would be out-of-date as soon as the caller
obtained it and massaging all architectures would be needed.
I don't see why the "number of waiters" needs to be known for this problem.
> Given enough processes in the waitqueue, the number of currently running
> processes effectively determines the number of processes to be started.
> And as those processes are already running, I don't see an effective
> procedure how we could _reduce_ the number of processes to be started.
By reducing the number of processes which can concurrently take the
semaphore? Confused.
-------------------------------------------------------
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_id\x10040&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
next prev parent reply other threads:[~2004-07-27 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 13:52 [PATCH] Limit number of concurrent hotplug processes Hannes Reinecke
2004-07-26 1:20 ` Andrew Morton
2004-07-26 6:19 ` Christian Borntraeger
2004-07-26 10:59 ` Hannes Reinecke
2004-07-26 20:18 ` Andrew Morton
2004-07-27 7:04 ` Hannes Reinecke
2004-07-27 7:24 ` Andrew Morton [this message]
2004-07-27 7:59 ` Hannes Reinecke
2004-07-27 8:34 ` Andrew Morton
2004-07-27 9:05 ` Hannes Reinecke
2004-07-27 9:28 ` Andrew Morton
2004-07-27 12:22 ` Hannes Reinecke
2004-07-28 7:12 ` Paul Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040727002409.68d49d7c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hare@suse.de \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).