From: Nick Piggin <nickpiggin@yahoo.com.au>
To: linux-arch@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: [patch][RFC] sched: optimise/cleanup resched_task, idle routines
Date: Sun, 27 Mar 2005 00:34:17 +1100 [thread overview]
Message-ID: <424564D9.9010306@yahoo.com.au> (raw)
In-Reply-To: <4245631A.1070806@yahoo.com.au>
Had this around for a while too. Quite a bit of arch work to get
through here, and I haven't done most of it (I probably butchered
ppc64, too).
It does seem to work OK on i386 and ia64, though. I'd like to get
confirmation that my approach is correct before putting more work
into it.
It can save locked memory ops and IPIs during scheduling operations.
I don't have access to any big systems that might most beneift from
the improved scalability, but it is worth a % or so on a dual Xeon
system here (on schedule happy workload).
But am I horribly misinformed? ;)
next prev parent reply other threads:[~2005-03-26 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 13:26 [patch] sched: remove scheduler locking from arch code Nick Piggin
2005-03-26 13:34 ` Nick Piggin [this message]
2005-03-26 13:34 ` [patch][RFC] sched: optimise/cleanup resched_task, idle routines Nick Piggin
2005-03-26 21:36 ` [patch] sched: remove scheduler locking from arch code David S. Miller
2005-03-27 3:03 ` Nick Piggin
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=424564D9.9010306@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=benh@kernel.crashing.org \
--cc=linux-arch@vger.kernel.org \
--cc=mingo@elte.hu \
/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