From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Thread Migration Preemption
Date: Fri, 06 Jul 2007 16:12:10 +1000 [thread overview]
Message-ID: <468DDD3A.6010308@yahoo.com.au> (raw)
In-Reply-To: <20070705215152.GA4865@Krystal>
Mathieu Desnoyers wrote:
> Thread Migration Preemption
>
> This patch adds the ability to protect critical sections from migration to
> another CPU without disabling preemption.
>
> This will be useful to minimize the amount of preemption disabling for the -rt
> patch. It will help leveraging improvements brought by the local_t types in
> asm/local.h (see Documentation/local_ops.txt). Note that the updates done to
> variables protected by migration_disable must be either atomic or protected from
> concurrent updates done by other threads.
>
> Typical use:
>
> migration_disable();
> local_inc(&__get_cpu_var(&my_local_t_var));
> migration_enable();
>
> Which will increment the variable atomically wrt the local CPU.
>
> Comments (such as how to integrate this in the already almost full
> preempt_count) are welcome.
This seems like way too much stuff to add just for this type of thing. Why
not just disable and reenable preempt? Surely local_inc is not going to take
so long that disabling preemption matters.
The task struct is not something we should just be carefree putting crap
into because it is seemingly free :(
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-07-06 6:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 21:51 [RFC] Thread Migration Preemption Mathieu Desnoyers
2007-07-05 22:46 ` Steven Rostedt
2007-07-06 6:12 ` Nick Piggin [this message]
2007-07-06 14:34 ` Mathieu Desnoyers
2007-07-06 14:34 ` Steven Rostedt
2007-07-06 15:43 ` Daniel Walker
2007-07-08 9:05 ` Nick Piggin
2007-07-10 23:39 ` Matt Mackall
2007-07-11 0:02 ` Nick Piggin
2007-07-11 0:36 ` Matt Mackall
2007-07-11 0:55 ` Mathieu Desnoyers
2007-07-11 1:15 ` Nick Piggin
2007-07-06 11:59 ` Andi Kleen
2007-07-06 14:41 ` Mathieu Desnoyers
2007-07-06 17:11 ` Andi Kleen
2007-07-11 4:57 ` Mathieu Desnoyers
2007-07-23 18:33 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2007-07-06 6:02 Oleg Nesterov
2007-07-06 14:23 ` Mathieu Desnoyers
2007-07-06 14:56 ` Oleg Nesterov
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=468DDD3A.6010308@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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