mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Nick Piggin" <npiggin@suse.de>
Cc: "Linux Memory Management List" <linux-mm@kvack.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Christoph Lameter" <clameter@sgi.com>
Subject: Re: [rfc] SLQB: YASA
Date: Thu, 3 Apr 2008 11:24:00 +0300	[thread overview]
Message-ID: <84144f020804030124m4cc0bc1en2e11218f1f8bdc55@mail.gmail.com> (raw)
In-Reply-To: <20080403081338.GA18337@wotan.suse.de>

Hi Nick,

On Thu, Apr 03, 2008 at 09:57:25AM +0200, Nick Piggin wrote:
> > It's a completely different design of the core allocator algorithms
> > really.
> >
> > It probably looks quite similar because I started with slub.c, but
> > really is just the peripheral supporting code and structure. I'm never
> > intending to try to go through the pain of incrementally changing SLUB
> > into SLQB. If SLQB is found to be a good idea, then it could maybe get
> > merged.

On Thu, Apr 3, 2008 at 11:13 AM, Nick Piggin <npiggin@suse.de> wrote:
>  And also I guess I don't think Christoph would be very happy about
>  it :) He loves higher order allocations :)
>
>  The high level choices are pretty clear and I simply think there might
>  be a better way to do it. I'm not saying it *is* better because I simply
>  don't know, and there are areas where the tradeoffs I've made means that
>  in some situations SLQB cannot match SLUB.

So do you disagree with Christoph's statement that we should fix page
allocator performance instead of adding queues to SLUB? I also don't
think higher order allocations are the answer for regular boxes but I
can see why they're useful for HPC people with huge machines.

                                     Pekka

  reply	other threads:[~2008-04-03  8:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  7:25 Nick Piggin
2008-04-03  7:45 ` Pekka Enberg
2008-04-03  7:57   ` Nick Piggin
2008-04-03  8:13     ` Nick Piggin
2008-04-03  8:24       ` Pekka Enberg [this message]
2008-04-03  8:32         ` Nick Piggin
2008-04-03  8:17     ` KOSAKI Motohiro
2008-04-03  8:26       ` Nick Piggin
2008-04-03  8:33         ` KOSAKI Motohiro
2008-04-03  8:41         ` Andi Kleen
2008-04-03 14:23 ` Nick Piggin
2008-04-03 19:04   ` Luiz Fernando N. Capitulino
2008-04-03 19:12 ` Christoph Lameter
2008-04-08 11:57   ` Nick Piggin
2008-04-08 18:51     ` Luiz Fernando N. Capitulino
2008-04-09  2:10       ` 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=84144f020804030124m4cc0bc1en2e11218f1f8bdc55@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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®