From: Pierre Habouzit <pierre.habouzit@intersec.com>
To: Avi Kivity <avi@redhat.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: Mon, 19 Dec 2011 11:26:05 +0100 [thread overview]
Message-ID: <20111219102605.GA28692@madism.org> (raw)
In-Reply-To: <4EEDADF1.3040305@redhat.com>
On Sun, Dec 18, 2011 at 11:10:09AM +0200, Avi Kivity wrote:
> 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).
It doesn't (use preempt notifiers) because it calls schedule directly
and can have its own processing before and after schedule() on his own.
Indeed, my goal is to have something like kernel/workqueues.c, kind of,
but for *userland*. The goal is to support things like Apple
pthread_workqueue_* stuff[1], and similar concepts of load-regulated
userland thread pools.
[1] http://people.freebsd.org/~sson/thrworkq/pthread_workqueue.3.txt
--
Intersec <http://www.intersec.com>
Pierre Habouzit <pierre.habouzit@intersec.com> | Chief Software Architect
Tél : +33 (0)1 5570 3346
Mob : +33 (0)6 1636 8131
Fax : +33 (0)1 5570 3332
37 Rue Pierre Lhomme
92400 Courbevoie
prev parent reply other threads:[~2011-12-19 10:26 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
2011-12-19 10:26 ` Pierre Habouzit [this message]
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=20111219102605.GA28692@madism.org \
--to=pierre.habouzit@intersec.com \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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