public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	davej@suse.de, marcelo@conectiva.com.br,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Linux HMT analysis
Date: Sun, 9 Dec 2001 11:17:29 +1100	[thread overview]
Message-ID: <20011209001729.GA3934@krispykreme> (raw)
In-Reply-To: <Pine.LNX.4.33.0112070033450.4486-100000@Appserv.suse.de> <E16C8Zk-0003if-00@the-village.bc.nu> <20011208214631.75573e9a.rusty@rustcorp.com.au>
In-Reply-To: <20011208214631.75573e9a.rusty@rustcorp.com.au>

 
> Anton, can you put the dbench graphs somewhere public?

Here they are:

http://samba.org/~anton/linux/HMT/

The machine is a 4 way RS64 (ppc64) box, with HMT enabled so Linux
thinks it has 8 cpus.

Since HMT is not an intel only problem it would be nice to solve this in
a slightly more generic way than #if defined(__i386__) && defined(CONFIG_SMP).
Otherwise there will shortly be yet another hack in the scheduler
surrounded by #ifdef CONFIG_PPC64_HMT :)

Its pretty obvious what they are trying to achieve (its always
preferrable to schedule 2 tasks on separate physical cpus rather than
sharing the same one), but their change does not seem to have the
required outcome.

Do we have any results showing the improvement this change made or did
we just accept the changes?

Anton

  reply	other threads:[~2001-12-09  1:22 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 17:39 Linux 2.4.17-pre5 Marcelo Tosatti
2001-12-06 19:07 ` Alan Cox
2001-12-06 23:38   ` Dave Jones
2001-12-07  0:09     ` Alan Cox
2001-12-08 10:46       ` Rusty Russell
2001-12-09  0:17         ` Anton Blanchard [this message]
2001-12-09  1:39           ` Linux HMT analysis Alan Cox
2001-12-09  1:41             ` Alan Cox
2001-12-09  0:31         ` Linux 2.4.17-pre5 Alan Cox
2001-12-09  1:58           ` Rusty Russell
2001-12-09  2:35             ` Davide Libenzi
2001-12-09  6:20               ` Rusty Russell
2001-12-09 16:24               ` Alan Cox
2001-12-09 19:48                 ` Davide Libenzi
2001-12-09 22:44                 ` Mike Kravetz
2001-12-09 23:50                   ` Davide Libenzi
2001-12-09 23:57                   ` Alan Cox
2001-12-19 22:16                 ` Pavel Machek
2001-12-20 19:10                   ` Davide Libenzi
2001-12-09 16:16             ` Alan Cox
2001-12-10  0:21               ` Rusty Russell
2001-12-10  0:41                 ` Alan Cox
2001-12-10  2:10                   ` Martin J. Bligh
2001-12-10  5:40                     ` Rusty Russell
2001-12-10  5:31                   ` Rusty Russell
2001-12-10  8:28                     ` Alan Cox
2001-12-10 23:12                       ` James Cleverdon
2001-12-10 23:30                         ` Alan Cox
2001-12-11  9:16                           ` Robert Varga
2001-12-11  9:23                             ` David Weinehall
2001-12-11  9:00                   ` Eric W. Biederman
2001-12-11 23:14                     ` Alan Cox
2001-12-09 19:38             ` Marcelo Tosatti
2001-12-09  9:47         ` arjan
2001-12-07 16:07     ` Marcelo Tosatti
2001-12-06 19:18 ` Matthias Andree
2001-12-06 19:05   ` Marcelo Tosatti
2001-12-06 21:14     ` Ben Greear
2001-12-06 21:58       ` David S. Miller
2001-12-06 22:24         ` Matthias Andree
2001-12-09 10:10         ` Eran Man
2001-12-06 20:14   ` Rik van Riel
2001-12-06 20:22     ` Jeff Garzik
2001-12-06 20:58     ` David S. Miller
2001-12-08  4:56       ` M. Edward Borasky
2001-12-08  5:41         ` David S. Miller

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=20011209001729.GA3934@krispykreme \
    --to=anton@samba.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@transmeta.com \
    /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