linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: David Rientjes <rientjes@google.com>
Cc: Pekka Enberg <penberg@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	hughd@google.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [GIT PULL] Lockless SLUB slowpaths for v3.1-rc1
Date: Wed, 3 Aug 2011 09:09:48 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1108030908100.24201@router.home> (raw)
In-Reply-To: <alpine.DEB.2.00.1108020938200.1114@chino.kir.corp.google.com>

On Tue, 2 Aug 2011, David Rientjes wrote:

> On Tue, 2 Aug 2011, Christoph Lameter wrote:
>
> > The per cpu partial lists only add the need for more memory if other
> > processors have to allocate new pages because they do not have enough
> > partial slab pages to satisfy their needs. That can be tuned by a cap on
> > objects.
> >
>
> The netperf benchmark isn't representative of a heavy slab consuming
> workload, I routinely run jobs on these machines that use 20 times the
> amount of slab.  From what I saw in the earlier posting of the per-cpu
> partial list patch, the min_partial value is set to half of what it was
> previously as a per-node partial list.  Since these are 16-core, 4 node
> systems, that would mean that after a kmem_cache_shrink() on a cache that
> leaves empty slab on the partial lists that we've doubled the memory for
> slub's partial lists systemwide.

Cutting down the potential number of empty slabs that we might possible
keep around because we have no partial slabs per node increases memory
usage?

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-08-03 14:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 22:47 Pekka Enberg
2011-07-29 15:04 ` Christoph Lameter
2011-07-29 23:18   ` Andi Kleen
2011-07-30  6:33     ` Eric Dumazet
2011-07-31 18:50   ` David Rientjes
2011-07-31 20:24     ` David Rientjes
2011-07-31 20:45       ` Pekka Enberg
2011-07-31 21:55         ` David Rientjes
2011-08-01  5:08           ` Pekka Enberg
2011-08-01 10:02             ` David Rientjes
2011-08-01 12:45               ` Pekka Enberg
2011-08-02  2:43                 ` David Rientjes
2011-08-01 12:06           ` Pekka Enberg
2011-08-01 15:55             ` Christoph Lameter
2011-08-02  4:05             ` David Rientjes
2011-08-02 14:15               ` Christoph Lameter
2011-08-02 16:24                 ` David Rientjes
2011-08-02 16:36                   ` Christoph Lameter
2011-08-02 20:02                     ` David Rientjes
2011-08-03 14:09                       ` Christoph Lameter [this message]
2011-08-08 20:04                         ` David Rientjes
2011-07-30 18:27 ` Linus Torvalds
2011-07-30 18:32   ` Linus Torvalds
2011-07-31 17:39     ` Andi Kleen
2011-08-01  0:22       ` KAMEZAWA Hiroyuki
2011-07-31 18:11     ` David Rientjes

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=alpine.DEB.2.00.1108030908100.24201@router.home \
    --to=cl@linux.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=torvalds@linux-foundation.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