From: Christoph Lameter <clameter@sgi.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
akpm@osdl.org, mm-commits@vger.kernel.org,
nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: + sched-use-tasklet-to-call-balancing.patch added to -mm tree
Date: Tue, 7 Nov 2006 10:18:44 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0611071015030.4249@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20061107095049.B3262@unix-os.sc.intel.com>
On Tue, 7 Nov 2006, Siddha, Suresh B wrote:
> tasklet_schedule doesn't schedule if there is already one scheduled.
Right.
/* Tasklets --- multithreaded analogue of BHs.
Main feature differing them of generic softirqs: tasklet
is running only on one CPU simultaneously.
Main feature differing them of BHs: different tasklets
may be run simultaneously on different CPUs.
Properties:
* If tasklet_schedule() is called, then tasklet is guaranteed
to be executed on some cpu at least once after this.
^^^^ Crap. Not equivalent. Must be guaranteed to run on the same cpu.
* If the tasklet is already scheduled, but its excecution is still not
started, it will be executed only once.
* If this tasklet is already running on another CPU (or schedule is called
from tasklet itself), it is rescheduled for later.
* Tasklet is strictly serialized wrt itself, but not
wrt another tasklets. If client needs some intertask synchronization,
he makes it with spinlocks.
*/
next prev parent reply other threads:[~2006-11-07 18:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611032205.kA3M5wmJ003178@shell0.pdx.osdl.net>
2006-11-07 7:32 ` Ingo Molnar
2006-11-07 17:44 ` Christoph Lameter
2006-11-07 17:31 ` Siddha, Suresh B
2006-11-07 17:55 ` Christoph Lameter
2006-11-07 17:50 ` Siddha, Suresh B
2006-11-07 18:18 ` Christoph Lameter [this message]
2006-11-07 19:17 ` Christoph Lameter
2006-11-07 20:31 ` Ingo Molnar
2006-11-07 20:59 ` Christoph Lameter
2006-11-07 21:35 ` Chen, Kenneth W
2006-11-07 21:49 ` Christoph Lameter
2006-11-10 6:18 ` Chen, Kenneth W
2006-11-10 18:50 ` Christoph Lameter
2006-11-10 21:38 ` Ingo Molnar
2006-11-11 1:01 ` Christoph Lameter
2006-11-11 2:05 ` Chen, Kenneth W
2006-11-11 2:51 ` Christoph Lameter
2006-11-13 4:03 ` Chen, Kenneth W
2006-11-13 5:44 ` Christoph Lameter
2006-11-13 6:40 ` Chen, Kenneth W
2006-11-14 1:06 ` [patch] sched domain: move sched group allocations to percpu area Siddha, Suresh B
2006-11-14 8:23 ` Ingo Molnar
2006-11-14 16:57 ` Christoph Lameter
2006-11-10 21:42 ` + sched-use-tasklet-to-call-balancing.patch added to -mm tree Ingo Molnar
2006-11-10 22:32 ` Siddha, Suresh B
2006-11-11 1:14 ` Christoph Lameter
2006-11-07 19:22 ` Christoph Lameter
2006-11-07 20:29 ` Ingo Molnar
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=Pine.LNX.4.64.0611071015030.4249@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=suresh.b.siddha@intel.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
all inboxes | Powered by JetHome®