From: Randy Dunlap <rdunlap@infradead.org>
To: Christoph Lameter <cl@linux.com>, Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
akpm@linux-foundation.org, Mel Gorman <mel@skynet.ie>,
andi@firstfloor.org, Rik van Riel <riel@redhat.com>,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>, Michal Hocko <mhocko@suse.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [RFC 0/7] Slab object migration for xarray V2
Date: Thu, 20 Dec 2018 14:32:14 -0800 [thread overview]
Message-ID: <e7a2e0a5-d5b7-a158-52a1-6aa230501a94@infradead.org> (raw)
In-Reply-To: <01000167cd1130c8-c9bebcb9-1f95-4f7c-b24a-90600d56c62f-000000@email.amazonses.com>
On 12/20/18 11:21 AM, Christoph Lameter wrote:
> To test apply this patchset and run a workload that uses lots of radix tree objects
>
>
> Then go to
>
> /sys/kernel/slab/radix_tree_node
>
> Inspect the number of total objects that the slab can handle
>
> cat total_objects
cat objects # ???
(as below) (just checking :)
>
> qmdr:/sys/kernel/slab/radix_tree_node# cat objects
> 868 N0=448 N1=168 N2=56 N3=196
>
> And the number of slab pages used for those
>
> cat slabs
>
> qmdr:/sys/kernel/slab/radix_tree_node# cat slabs
> 31 N0=16 N1=6 N2=2 N3=7
>
>
> Perform a cache shrink operation
>
> echo 1 >shrink
>
>
> Now see how the slab has changed:
>
> qmdr:/sys/kernel/slab/radix_tree_node# cat slabs
> 30 N0=15 N1=6 N2=2 N3=7
> qmdr:/sys/kernel/slab/radix_tree_node# cat objects
> 713 N0=349 N1=141 N2=52 N3=171
--
~Randy
next prev parent reply other threads:[~2018-12-20 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 19:21 Christoph Lameter
2018-12-20 19:21 ` Christoph Lameter
2018-12-20 22:32 ` Randy Dunlap [this message]
2018-12-21 1:43 ` [RFC 5/7] Slab defrag core Christopher Lameter
2018-12-21 1:43 ` Christopher 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=e7a2e0a5-d5b7-a158-52a1-6aa230501a94@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=penberg@cs.helsinki.fi \
--cc=riel@redhat.com \
--cc=willy@infradead.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