From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.0 batch scheduling, HT aware
Date: 30 Dec 2003 00:35:26 GMT [thread overview]
Message-ID: <bsqh8e$fm1$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 200312240909.19006.kernel@kolivas.org
In article <200312240909.19006.kernel@kolivas.org>,
Con Kolivas <kernel@kolivas.org> wrote:
| On Wed, 24 Dec 2003 02:51, bill davidsen wrote:
| > There are two goals here. Not having a batch process on one siling makes
| > sense, and I'm going to try Con's patch after I try Nick's latest.
| > Actually, if they play nicely I would use both, batch would be very
| > useful for nightly report generation on servers.
|
| No hope of them playing nicely, but at some later stage I might resync on top
| of Nick's work if I like the direction it takes (which looks likely!)
|
| > But WRT the whole HT scheduling, it would seem that ideally you want to
| > schedule the two (or N) processes which have the lowest aggregate cache
| > thrash, if you had a way to determine that. I suspect that a process
| > which had a small itterative inner loop with a code+data footprint of
| > 2-3k would coexist well with almost anything else. Minimizing the FPU
| > contention also would improve performance, no doubt. I don't know that
| > there are the tools at the moment to get this information, but it seems
| > as though until it's available any scheduling will be working in the
| > dark to some extent.
|
| Impossible with current tools. Only userspace would have a chance of
| predicting this and the simple rule we work off is that userspace can't be
| trusted so this does not appear doable in the foreseeable future.
Glad you agree, but this makes improvement dificult.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-12-30 0:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:38 [PATCH] 2.6.0 batch scheduling, HT aware Con Kolivas
2003-12-23 1:11 ` Nick Piggin
2003-12-23 1:24 ` Con Kolivas
2003-12-23 1:36 ` Nick Piggin
2003-12-23 2:42 ` Con Kolivas
2003-12-23 2:57 ` Nick Piggin
2003-12-23 3:15 ` Con Kolivas
2003-12-23 3:16 ` Con Kolivas
2003-12-26 23:03 ` Pavel Machek
2003-12-23 15:51 ` bill davidsen
2003-12-23 22:09 ` Con Kolivas
2003-12-30 0:35 ` bill davidsen [this message]
2004-01-02 20:10 ` Bill Davidsen
2003-12-26 22:56 ` Pavel Machek
2003-12-26 23:42 ` Con Kolivas
2003-12-26 23:49 ` Con Kolivas
2003-12-27 11:09 ` Pavel Machek
2003-12-27 11:15 ` Con Kolivas
2003-12-30 0:29 ` bill davidsen
2003-12-29 7:02 ` Nick Piggin
2003-12-29 12:49 ` Pavel Machek
2003-12-27 8:52 ` Mika Penttilä
2003-12-30 0:32 ` bill davidsen
2004-01-02 20:05 ` Bill Davidsen
2004-01-02 20:56 ` Davide Libenzi
2004-01-02 21:10 ` Valdis.Kletnieks
2004-01-02 23:34 ` Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 1:59 Nakajima, Jun
2003-12-23 2:40 ` Nick Piggin
2003-12-23 5:33 Nakajima, Jun
2003-12-23 10:13 ` 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='bsqh8e$fm1$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.