From: Shawn Joo <sjoo@nvidia.com>
To: Glauber Costa <glommer@parallels.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 20:55:58 +0800 [thread overview]
Message-ID: <5F2C6DA655B36C43B21C7FB179CEC9F4E3F157BDF1@HKMAIL02.nvidia.com> (raw)
In-Reply-To: <501A77A4.1050005@parallels.com>
>> 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?
Thanks,
Seongho(Shawn)
-----Original Message-----
From: Glauber Costa [mailto:glommer@parallels.com]
Sent: Thursday, August 02, 2012 9:51 PM
To: Shawn Joo
Cc: cl@linux-foundation.org; penberg@kernel.org; mpm@selenic.com; linux-mm@kvack.org
Subject: Re: [question] how to increase the number of object on cache?
On 08/02/2012 04:20 PM, Shawn Joo wrote:
> Dear Experts,
>
>
>
> I would like to know a mechanism, how to increase the number of object
> and where the memory is from.
>
> (because when cache is created by "kmem_cache_create", there is only
> object size, but no number of the object)
>
> For example, "size-65536" does not have available memory from below dump.
>
> In that state, if memory allocation is requested to "size-65536",
>
> 1. How to allocate/increase the number of object on "size-65536"?
>
> 2. Where is the new allocated memory from? (from buddy?)
>
>
I am not sure I fully understand your question. But if you refer to something like "from where does the object allocators get their memory when more is needed", then yes, they will allocate the necessary number of pages from the standard page allocator.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
--
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>
next prev parent reply other threads:[~2012-08-02 12:56 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 [this message]
2012-08-02 13:02 ` Glauber Costa
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=5F2C6DA655B36C43B21C7FB179CEC9F4E3F157BDF1@HKMAIL02.nvidia.com \
--to=sjoo@nvidia.com \
--cc=cl@linux-foundation.org \
--cc=glommer@parallels.com \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.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