From: Benjamin LaHaise <bcrl@redhat.com>
To: Martin Maletinsky <maletinsky@scs.ch>
Cc: kernelnewbies@nl.linux.org, linux-mm@kvack.org
Subject: Re: Slab allocator - questions
Date: Wed, 3 Apr 2002 14:32:28 -0500 [thread overview]
Message-ID: <20020403143227.A6301@redhat.com> (raw)
In-Reply-To: <3CAAC471.ED65E4C9@scs.ch>; from maletinsky@scs.ch on Wed, Apr 03, 2002 at 10:59:29AM +0200
Hello,
On Wed, Apr 03, 2002 at 10:59:29AM +0200, Martin Maletinsky wrote:
...
> 2) Why are there general caches up to a size of 128K byte? Since a slab
> consists of physically contiguous pages, one might call right into the
> buddy system to get chunks of memory that are a multiple of a page size.
> What is the benefit of allocating memory chunks that are a multiple of
> a page size by using kmalloc()/kmem_cache_alloc() rather than
> get_free_pages?
Memory fragmentation. By grouping objects of the same type and similar
lifetimes, slab helps prevent the pinning of many individual pages across
the system. Since slab allocations cannot be relocated, this helps when
other allocations need to obtain non-0 order pages.
> 3) How does the slab cache allocator deal with high memory pages in 2.4.x
> (i.e. pages for which no KSEG address exists)?
They are not used.
-ben
--
"A man with a bass just walked in,
and he's putting it down
on the floor."
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-04-03 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 8:59 Martin Maletinsky
2002-04-03 19:32 ` Benjamin LaHaise [this message]
2002-04-04 6:19 ` Martin Maletinsky
2002-04-04 22:30 ` Benjamin LaHaise
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=20020403143227.A6301@redhat.com \
--to=bcrl@redhat.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mm@kvack.org \
--cc=maletinsky@scs.ch \
/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