linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@parallels.com>
To: Shawn Joo <sjoo@nvidia.com>
Cc: "cl@linux-foundation.org" <cl@linux-foundation.org>,
	"penberg@kernel.org" <penberg@kernel.org>,
	"mpm@selenic.com" <mpm@selenic.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [question] how to increase the number of object on cache?
Date: Thu, 2 Aug 2012 17:02:01 +0400	[thread overview]
Message-ID: <501A7A49.6070506@parallels.com> (raw)
In-Reply-To: <5F2C6DA655B36C43B21C7FB179CEC9F4E3F157BDF1@HKMAIL02.nvidia.com>

On 08/02/2012 04:55 PM, Shawn Joo wrote:
>>> then yes, they will allocate the necessary number of pages from the standard page allocator.
> Who is "the standard page allocator" for cache in /proc/slabinfo, e.g. "size-65536" ?
> I believe one of allocator is buddy. who else?
> 
The generic and algorithm-neutral answer to this is "whoever would
handle alloc_pages()".
In the specific case, yes, this is the buddy allocator.

Take a look at mm/slab.c, for instance:

When a cache can't service an allocation, it does:

  cache_grow()
  -> kmem_getpages()
    -> alloc_pages_exact_node()


--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-08-02 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 12:20 Shawn Joo
2012-08-02 12:50 ` Glauber Costa
2012-08-02 12:55   ` Shawn Joo
2012-08-02 13:02     ` Glauber Costa [this message]
2012-08-02 13:50 ` Michal Hocko
2012-08-02 13:54 ` Christoph Lameter

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=501A7A49.6070506@parallels.com \
    --to=glommer@parallels.com \
    --cc=cl@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.com \
    --cc=penberg@kernel.org \
    --cc=sjoo@nvidia.com \
    /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