From: Shawn Joo <sjoo@nvidia.com>
To: "cl@linux-foundation.org" <cl@linux-foundation.org>,
"penberg@kernel.org" <penberg@kernel.org>,
"mpm@selenic.com" <mpm@selenic.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [question] how to increase the number of object on cache?
Date: Thu, 2 Aug 2012 20:20:25 +0800 [thread overview]
Message-ID: <5F2C6DA655B36C43B21C7FB179CEC9F4E3F157BDEE@HKMAIL02.nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]
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 believe it is hard to explain with simple word, any advice will be very helpful.
cat /proc/buddyinfo
Node 0, zone Normal 949 0 0 2 3 3 0 0 1 1 0
cat /proc/slabinfo
slabinfo - version: 2.1
# name <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> : tunables <limit> <batchcount> <sharedfactor> : slabdata <active_slabs> <num_slabs> <sharedavail>
size-4194304 0 0 4194304 1 1024 : tunables 1 1 0 : slabdata 0 0 0
size-2097152 0 0 2097152 1 512 : tunables 1 1 0 : slabdata 0 0 0
size-1048576 0 0 1048576 1 256 : tunables 1 1 0 : slabdata 0 0 0
size-524288 0 0 524288 1 128 : tunables 1 1 0 : slabdata 0 0 0
size-262144 0 0 262144 1 64 : tunables 1 1 0 : slabdata 0 0 0
size-131072 1 1 131072 1 32 : tunables 8 4 0 : slabdata 1 1 0
size-65536 4 4 65536 1 16 : tunables 8 4 0 : slabdata 4 4 0
Thanks,
Seongho(Shawn)
-----------------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------------
[-- Attachment #2: Type: text/html, Size: 12327 bytes --]
next reply other threads:[~2012-08-02 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 12:20 Shawn Joo [this message]
2012-08-02 12:50 ` Glauber Costa
2012-08-02 12:55 ` Shawn Joo
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=5F2C6DA655B36C43B21C7FB179CEC9F4E3F157BDEE@HKMAIL02.nvidia.com \
--to=sjoo@nvidia.com \
--cc=cl@linux-foundation.org \
--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