From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: Matt Mackall <mpm@selenic.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SLOB allocator imcompatible SLAB
Date: Tue, 26 Jun 2007 14:06:15 +1000 [thread overview]
Message-ID: <468090B7.2080200@yahoo.com.au> (raw)
In-Reply-To: <m2ejk05y7c.wl%ysato@users.sourceforge.jp>
Yoshinori Sato wrote:
> At Fri, 22 Jun 2007 09:56:35 -0500,
> Matt Mackall wrote:
>
>>On Fri, Jun 22, 2007 at 05:08:07PM +0900, Yoshinori Sato wrote:
>>
>>>Because the page which SLOB allocator got does not have PG_slab,
>>
>>This is for a NOMMU system?
>
>
> Yes.
>
>
>>You're using an old kernel with an old version of SLOB. SLOB in newer
>>kernels actually sets per-page flags. Nick, can you see any reason not
>>to s/PG_active/PG_slab/ in the current code?
The problem with this is that PG_private is used only for the SLOB
part of the allocator and not the bigblock part.
We _could_ just bite the bullet and have SLOB set PG_slab, however
that would encouarage more users of this flag which we should hope
to get rid of one day.
The real problem is that nommu wants to get the size of either
kmalloc or alloc_pages objects and it needs to differentiate
between them. So I would rather nommu to take its own page flag
(could overload PG_swapcache, perhaps?), and set that flag on
pages it allocates directly, then uses that to determine whether
to call ksize or not.
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-06-26 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 8:08 [PATCH] SLOB allocator imcompatible SLAB Yoshinori Sato
2007-06-22 14:56 ` Matt Mackall
2007-06-25 6:45 ` Yoshinori Sato
2007-06-26 4:06 ` Nick Piggin [this message]
2007-06-26 4:56 ` Matt Mackall
2007-06-26 5:00 ` Nick Piggin
2007-06-26 5:24 ` Matt Mackall
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=468090B7.2080200@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=ysato@users.sourceforge.jp \
/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