mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>
Cc: "Mel Gorman" <mel@csn.ul.ie>,
	"Christoph Lameter" <cl@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SLUB: use page allocator for PAGE_SIZE requests
Date: Sat, 22 Nov 2008 13:37:45 +0100	[thread overview]
Message-ID: <19f34abd0811220437w3e20f824m27578618777ae8b7@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0811220435r38e749e3o425d994912fc92ea@mail.gmail.com>

On Sat, Nov 22, 2008 at 1:35 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> On Sat, Nov 22, 2008 at 1:32 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>> From 4d526db4781aaab86cb79ff8135bb0e2bc560598 Mon Sep 17 00:00:00 2001
>> From: Vegard Nossum <vegard.nossum@gmail.com>
>> Date: Sat, 22 Nov 2008 13:27:54 +0100
>> Subject: [PATCH] SLUB: use page allocator for PAGE_SIZE requests
>>
>> It seems strange that we should use the page allocator for
>> requests of (PAGE_SIZE + 1) bytes or more, and not for requests
>> that are exactly PAGE_SIZE.
>
> Actually, there are some more places that need to be fixed. I think
> I'll send an updated patch that fixes all of them.

ACTUALLY, please ignore whole thread. I now read the commit message of

commit 331dc558fa020451ff773973cee855fd721aa88e
Author: Christoph Lameter <clameter@sgi.com>
Date:   Thu Feb 14 14:28:09 2008 -0800

    slub: Support 4k kmallocs again to compensate for page allocator slowness

:-/

Sorry for the noise.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

      reply	other threads:[~2008-11-22 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 12:32 Vegard Nossum
2008-11-22 12:35 ` Vegard Nossum
2008-11-22 12:37   ` Vegard Nossum [this message]

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=19f34abd0811220437w3e20f824m27578618777ae8b7@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=penberg@cs.helsinki.fi \
    /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®