public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Anton Blanchard <anton@samba.org>
Cc: Olaf Hering <olh@suse.de>, Andrew Morton <akpm@osdl.org>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PPC64] Improved VSID allocation algorithm
Date: Thu, 30 Sep 2004 17:01:51 +1000	[thread overview]
Message-ID: <20040930070151.GG21889@zax> (raw)
In-Reply-To: <20040930064037.GA3167@krispykreme.ozlabs.ibm.com>

On Thu, Sep 30, 2004 at 04:40:37PM +1000, Anton Blanchard wrote:
>  
> > This patch went into 2.6.9-rc2-bk2, and my p640 does not boot anymore.
> > Hangs after 'returning from prom_init', wants a power cycle.
> 
> How much memory do you have? We might be filling up a hpte bucket
> completely with certain amounts of memory.

Bugger, bugger, bugger bugger.  That's it.  Just ran 4GB linear
mapping with 4k pages through by hash scattering simulator - max
bucket load is 2 with the old algo and 16 with the new one.  Well, we
just found the first case where the new algorithm scatters
significantly worse than the old one.  It would be something this
dire, wouldn't it.

-- 
David Gibson			| For every complex problem there is a
david AT gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

  parent reply	other threads:[~2004-09-30  7:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13  4:11 [PPC64] Improved VSID allocation algorithm David Gibson
2004-09-29 19:47 ` Olaf Hering
2004-09-30  0:38   ` David Gibson
2004-09-30  5:53     ` Olaf Hering
2004-09-30  6:35       ` David Gibson
2004-09-30  6:40   ` Anton Blanchard
2004-09-30  6:49     ` Olaf Hering
2004-09-30  7:01     ` David Gibson [this message]
2004-09-30  8:05       ` David Gibson
2004-09-30  8:20         ` Olaf Hering

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=20040930070151.GG21889@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=olh@suse.de \
    --cc=paulus@samba.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