From: Christoph Lameter <cl@linux.com>
To: JoonSoo Kim <js1304@gmail.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Pekka Enberg <penberg@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Wanpeng Li <liwanp@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 3/5] slab: restrict the number of objects in a slab
Date: Sun, 20 Oct 2013 18:08:44 +0000 [thread overview]
Message-ID: <00000141d70e0e22-bd66f3af-822a-47dd-bbd9-fe68ad8da2ff-000000@email.amazonses.com> (raw)
In-Reply-To: <CAAmzW4Mzx0FWP6KK7gk88c07RP46WaA9i5DePnzSWt7XP6qQNw@mail.gmail.com>
On Sat, 19 Oct 2013, JoonSoo Kim wrote:
> > Ok so that results in a mininum size object size of 2^(12 - 8) = 2^4 ==
> > 16 bytes on x86. This is not true for order 1 pages (which SLAB also
> > supports) where we need 32 bytes.
>
> According to current slab size calculating logic, slab whose object size is
> less or equal to 16 bytes use only order 0 page. So there is no problem.
Ok then lets add a VM_BUG_ON to detect the situation when someone tries
something different.
> > Problems may arise on PPC or IA64 where the page size may be larger than
> > 64K. With 64K we have a mininum size of 2^(16 - 8) = 256 bytes. For those
> > arches we may need 16 bit sized indexes. Maybe make that compile time
> > determined base on page size? > 64KByte results in 16 bit sized indexes?
>
> Okay. I will try it.
Again compile time. You had runtime in some earlier patches which adds new
branches to key functions.
--
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:[~2013-10-20 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 6:03 [PATCH v2 0/5] slab: implement byte sized indexes for the freelist of " Joonsoo Kim
2013-10-17 6:03 ` [PATCH v2 1/5] slab: factor out calculate nr objects in cache_estimate Joonsoo Kim
2013-10-17 19:03 ` Christoph Lameter
2013-10-17 6:03 ` [PATCH v2 2/5] slab: introduce helper functions to get/set free object Joonsoo Kim
2013-10-17 6:03 ` [PATCH v2 3/5] slab: restrict the number of objects in a slab Joonsoo Kim
2013-10-17 19:01 ` Christoph Lameter
2013-10-18 15:12 ` JoonSoo Kim
2013-10-20 18:08 ` Christoph Lameter [this message]
2013-10-17 6:03 ` [PATCH v2 4/5] slab: introduce byte sized index for the freelist of " Joonsoo Kim
2013-10-17 6:03 ` [PATCH v2 5/5] slab: make more slab management structure off the slab Joonsoo Kim
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=00000141d70e0e22-bd66f3af-822a-47dd-bbd9-fe68ad8da2ff-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.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