linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: linux-mm@kvack.org
Subject: simple slab alloc question
Date: Sun, 10 Oct 1999 18:09:47 -0400	[thread overview]
Message-ID: <38010EAB.ACC45162@pobox.com> (raw)

kmalloc seems to allocate against various kmem_cache sizes: 32,
64...1024...65536...

Does this mean that allocations of various sizes are stored in different
"buckets"?  Would that not reduce fragmentation and the need for a zone
allocator?

Enlightenment from MM gurus appreciated :)

Regards,

	Jeff




-- 
Custom driver development	|    Never worry about theory as long
Open source programming		|    as the machinery does what it's
				|    supposed to do.  -- R. A. Heinlein
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

             reply	other threads:[~1999-10-10 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-10 22:09 Jeff Garzik [this message]
1999-10-11 11:10 ` Andi Kleen
1999-10-11 18:11   ` Rik van Riel
1999-10-11 22:19     ` Stephen C. Tweedie

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=38010EAB.ACC45162@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-mm@kvack.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