From: "J.C. Pizarro" <jcpiza@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Improved idea, to use NR_CPUS task_migrators for SMPs.
Date: Sat, 23 Feb 2008 00:57:15 +0100 [thread overview]
Message-ID: <998d0e4a0802221557s23abba9as6407c6ced1eb036f@mail.gmail.com> (raw)
In-Reply-To: <998d0e4a0802221457g5aee11feo1da2f140a02478b8@mail.gmail.com>
On 2008/2/22, J.C. Pizarro <jcpiza@gmail.com>, i wrote:
> For comprension, unlocking
> some lockers of the task_migrators and inmediately switching CPU to
> migrators is similar to quick awakening of migration_thread.
I'm sorry, it's wrong, the correct is in reverse, locking when it wants to enter
and unlocking when it's exited.
prev parent reply other threads:[~2008-02-22 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 22:57 J.C. Pizarro
2008-02-22 23:57 ` J.C. Pizarro [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=998d0e4a0802221557s23abba9as6407c6ced1eb036f@mail.gmail.com \
--to=jcpiza@gmail.com \
--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
all inboxes | Powered by JetHome®