From: Avi Kivity <avi@redhat.com>
To: Pierre Habouzit <pierre.habouzit@intersec.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] sched: allow preempt notifiers to self-unregister.
Date: Sun, 18 Dec 2011 11:10:09 +0200 [thread overview]
Message-ID: <4EEDADF1.3040305@redhat.com> (raw)
In-Reply-To: <1324052151-3714-1-git-send-email-pierre.habouzit@intersec.com>
On 12/16/2011 06:15 PM, Pierre Habouzit wrote:
> As a background, this need is because I have some kind of module code
> that uses this facility to evaluate how many of a group of threads are
> concurrently running (to regulate a pool of threads).
>
That's what's cmwq is supposed to be doing (and that too should be using
preempt notifiers, IMO).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-18 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 16:15 [PATCH] sched: allow preempt notifiers to self-unregister Pierre Habouzit
2011-12-16 17:09 ` Peter Zijlstra
2011-12-16 17:25 ` Pierre Habouzit
2011-12-16 17:33 ` Peter Zijlstra
2011-12-16 17:42 ` Pierre Habouzit
2011-12-18 9:10 ` Avi Kivity [this message]
2011-12-19 10:26 ` Pierre Habouzit
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=4EEDADF1.3040305@redhat.com \
--to=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pierre.habouzit@intersec.com \
/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