linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: David Miller <davem@davemloft.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: LMB regression...
Date: Thu, 24 Apr 2008 16:35:33 +1000	[thread overview]
Message-ID: <1209018933.22532.0.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20080423.232419.193712136.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

On Wed, 2008-04-23 at 23:24 -0700, David Miller wrote:
> Paul, I finally got around to testing your changeset on sparc64, it
> breaks things:
> 
> commit d9024df02ffe74d723d97d552f86de3b34beb8cc
> Author: Paul Mackerras <paulus@samba.org>
> Date:   Sat Apr 12 15:20:59 2008 +1000
> 
>     [LMB] Restructure allocation loops to avoid unsigned underflow
>  ...    
> 
> Specifically, you removed the aligning of the size argument given to
> lmb_add_region() in the lmb allocators, and that is critical when
> allocating many small chunks, we run out of LMB slots otherwise
> and allocations start failing.
> 
> I added the alignment there as a bug fix earlier:
> 
> commit eea89e13a9c61d3928223d2f9bf2295e22e0efb6
> Author: David S. Miller <davem@davemloft.net>
> Date:   Wed Feb 13 16:57:09 2008 -0800
> 
>     [LMB]: Fix bug in __lmb_alloc_base().
>     
>     We need to check lmb_add_region() for errors, it can run out
>     of regions etc.
>     
>     Also, the size needs to be padded to the given alignment
>     or else the lmb.reserved regions don't get expanded and
>     instead we get tons of holes and eventually run out of
>     regions prematurely.
>     
>     Signed-off-by: David S. Miller <davem@davemloft.net>
> 
> Please be more careful in the future :-(
> 
> I find it quite ironic that you spent so much time and effort fixing
> an absolutely totally theoretical bug that nobody was triggering, and
> in the process reintroduced a real one that triggers immediately on
> real systems, and that had even been explicitly fixed previously.

Sounds like we need a test suite :)

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-24  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24  6:24 LMB regression David Miller
2008-04-24  6:35 ` Michael Ellerman [this message]
2008-04-24  6:40   ` David Miller
2008-04-24  6:56 ` Paul Mackerras
2008-04-24  7:01   ` David 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=1209018933.22532.0.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@ozlabs.org \
    --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;
as well as URLs for NNTP newsgroup(s).