From: Nick Piggin <piggin@cyberone.com.au>
To: David Nielsen <Lovechild@foolclan.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Nick's scheduler v19
Date: Sat, 15 Nov 2003 20:14:18 +1100 [thread overview]
Message-ID: <3FB5EE6A.8080801@cyberone.com.au> (raw)
In-Reply-To: <1067175079.664.7.camel@pilot.stavtrup-st.dk>
http://www.kerneltrap.org/~npiggin/v19/
Quite a few changes. Although inter node and intra node migration is
generally reduced in my patches, it seems probably context switching
is hurting more. This would explain the decreased system time and
increased user time - the user code is thrashing the cache more.
I haven't addressed that problem yet, although I have removed the
last (I think) major source of cacheline dirtying between CPUs. I say
major, but it was difficult to measure a difference on a 16-way NUMAQ.
For desktop users, microsecond accounting. This currently incurs a
bit of unneeded overhead because I have to convert from 64-bit nanoseconds
to 32-bit microseconds everywhere. I'm using microseconds because a 32-bit
value can store a maximum interval of about 4 seconds in nanoseconds, which
causes me all sorts of overflow problems.
I'm pleased to have had good results with HZ timing up until now. I think
this helps interactivity but I haven't had many problems with it myself.
Its against mm3 but I can do a patch against Linus' tree.
Best regards,
Nick
next parent reply other threads:[~2003-11-15 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1065350173.4946.5.camel@pilot.stavtrup-st.dk>
[not found] ` <3F80DF3C.8010406@cyberone.com.au>
[not found] ` <3F81123F.4040609@cyberone.com.au>
[not found] ` <3F811E02.3060803@cyberone.com.au>
[not found] ` <3F8140CF.9050603@cyberone.com.au>
[not found] ` <1065612151.4782.4.camel@pilot.stavtrup-st.dk>
[not found] ` <3F9907EB.7050700@cyberone.com.au>
[not found] ` <1067175079.664.7.camel@pilot.stavtrup-st.dk>
2003-11-15 9:14 ` Nick Piggin [this message]
[not found] ` <1068899953.5033.1.camel@nosferatu.lan>
2003-11-15 13:14 ` 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=3FB5EE6A.8080801@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=Lovechild@foolclan.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®