mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "David S. Miller" <davem@davemloft.net>
Cc: heiko.carstens@de.ibm.com, hare@suse.de, linux-kernel@vger.kernel.org
Subject: Re: calibrate_migration_costs takes ages on s390
Date: Mon, 13 Feb 2006 11:54:21 +0100	[thread overview]
Message-ID: <20060213105421.GB17173@elte.hu> (raw)
In-Reply-To: <20060213.023430.126649129.davem@davemloft.net>


* David S. Miller <davem@davemloft.net> wrote:

> Things are not as slow, but definitely slow on sparc64 too, and it's 
> also due to the migration cost calculations.
> 
> It's also really bad that it's using vmalloc(), for one thing, because 
> this thrashes the TLB (some of us have 64-entry software replaced 
> TLBs) and also because you can make no guarentees about how well the 
> backing physical pages will distribute into the L2 cache.

the TLB trashing is intended, to calculate the worst-case migration 
cost. If userspace is TLB-intensive, it will trash TLBs just as much.

> As a result, wildly different run-to-run results can be expected 
> particularly for systems with 1-way or 2-way set assosciative L2 
> caches, which are common on sparc64.  I don't know about s390.

s390 is clearly a special-base, being a virtual platform. But the 
calibration should be improved to work better on sparc64.

Do things get better if you fill out include/asm-sparc64/system.h's 
sched_cacheflush() function, to flush the L2 cache? That should at least 
make the cache state more or less reproducable across runs.

	Ingo

  reply	other threads:[~2006-02-13 10:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 10:26 Heiko Carstens
2006-02-13 10:34 ` David S. Miller
2006-02-13 10:54   ` Ingo Molnar [this message]
2006-02-13 20:57     ` David S. Miller
2006-02-13 10:46 ` Ingo Molnar
2006-02-13 16:13   ` Heiko Carstens
2006-02-13 23:42   ` Olaf Hering
2006-02-14  0:08     ` Olaf Hering
2006-02-14  8:09       ` Heiko Carstens
2006-02-14 10:56         ` Heiko Carstens
2006-02-14 12:35           ` Ingo Molnar
2006-02-14 12:37             ` Ingo Molnar
2006-02-16  6:27   ` Heiko Carstens

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=20060213105421.GB17173@elte.hu \
    --to=mingo@elte.hu \
    --cc=davem@davemloft.net \
    --cc=hare@suse.de \
    --cc=heiko.carstens@de.ibm.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®