From: John Hawkes <hawkes@google.engr.sgi.com>
To: Andrew Morton <akpm@osdl.org>,
John Hawkes <hawkes@google.engr.sgi.com>,
"Martin J. Bligh" <mbligh@aracnet.com>
Cc: johnstul@us.ibm.com, linux-kernel@vger.kernel.org, mingo@elte.hu,
lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: [RFC][PATCH] 2.6.0-test11 sched_clock() broken for "drifty ITC"
Date: Mon, 29 Dec 2003 12:16:22 -0800 (PST) [thread overview]
Message-ID: <200312292016.MAA01670@google.engr.sgi.com> (raw)
In-Reply-To: 200312291851.KAA25312@google.engr.sgi.com
> [ Martin Bligh writes: ]
> Is there any harm in dropping the first part of your patch, ie.
...
> > diff -X /home/hawkes/Patches/ignore.dirs -Naur linux-2.6.0/arch/i386/kernel/timers/timer_tsc.c linux-2.6.0-schedclock2/arch/i386/kernel/timers/timer_tsc.c
...
> and leaving the rest of it? the CONFIG_NUMA affects both NUMA-Q and Summit,
> BTW, which uses the cyclone timer, so it gets even more complex ;-)
No, no harm. Leaving out that timer_tsc.c part means only that i386
CONFIG_NUMA continues to use "jiffies" as the timebase, which is a
low-resolution timebase and may affect the quality of some of the
interactive scheduling decisions.
John Hawkes
prev parent reply other threads:[~2003-12-29 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 20:44 [RFC][PATCH] 2.6.0-test11 sched_clock() broken for "drifty ITC" John Hawkes
2003-12-18 22:37 ` john stultz
2003-12-20 10:41 ` Andrew Morton
2003-12-20 10:50 ` Ingo Molnar
2003-12-20 14:57 ` Nick Piggin
2003-12-20 15:05 ` Andrew Morton
2003-12-20 15:12 ` Nick Piggin
2003-12-20 16:36 ` Ingo Molnar
2003-12-20 21:41 ` Zwane Mwaikambo
2003-12-29 18:51 ` John Hawkes
2003-12-29 19:32 ` [Lse-tech] " Martin J. Bligh
2003-12-29 20:16 ` John Hawkes [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=200312292016.MAA01670@google.engr.sgi.com \
--to=hawkes@google.engr.sgi.com \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--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