From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christoph Lameter <clameter@sgi.com>
Cc: netdev@vger.kernel.org, linux-mm@kvack.org,
David Miller <davem@davemloft.net>
Subject: Re: [RFC][PATCH 5/6] slab: kmem_cache_objs_to_pages()
Date: Thu, 30 Nov 2006 20:03:19 +0100 [thread overview]
Message-ID: <1164913399.6588.158.camel@twins> (raw)
In-Reply-To: <Pine.LNX.4.64.0611301103340.23913@schroedinger.engr.sgi.com>
On Thu, 2006-11-30 at 11:06 -0800, Christoph Lameter wrote:
> On Thu, 30 Nov 2006, Peter Zijlstra wrote:
>
> > Right, perhaps my bad in wording the intent; the needed information is
> > how many more pages would I need to grow the slab with in order to store
> > so many new object.
>
> Would you not have to take objects currently available in
> caches into account? If you are short on memory then a flushing of all the
> caches may give you the memory you need (especially on a system with a
> large number of processors).
Sure, but this gives a safe upper bound.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christoph Lameter <clameter@sgi.com>
Cc: netdev@vger.kernel.org, linux-mm@kvack.org,
David Miller <davem@davemloft.net>
Subject: Re: [RFC][PATCH 5/6] slab: kmem_cache_objs_to_pages()
Date: Thu, 30 Nov 2006 20:03:19 +0100 [thread overview]
Message-ID: <1164913399.6588.158.camel@twins> (raw)
In-Reply-To: <Pine.LNX.4.64.0611301103340.23913@schroedinger.engr.sgi.com>
On Thu, 2006-11-30 at 11:06 -0800, Christoph Lameter wrote:
> On Thu, 30 Nov 2006, Peter Zijlstra wrote:
>
> > Right, perhaps my bad in wording the intent; the needed information is
> > how many more pages would I need to grow the slab with in order to store
> > so many new object.
>
> Would you not have to take objects currently available in
> caches into account? If you are short on memory then a flushing of all the
> caches may give you the memory you need (especially on a system with a
> large number of processors).
Sure, but this gives a safe upper bound.
next prev parent reply other threads:[~2006-11-30 19:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 10:14 [RFC][PATCH 0/6] VM deadlock avoidance -v9 Peter Zijlstra
2006-11-30 10:14 ` [RFC][PATCH 1/6] mm: slab allocation fairness Peter Zijlstra
2006-11-30 18:52 ` Christoph Lameter
2006-11-30 18:52 ` Christoph Lameter
2006-11-30 18:55 ` Peter Zijlstra
2006-11-30 18:55 ` Peter Zijlstra
2006-11-30 19:33 ` Christoph Lameter
2006-11-30 19:33 ` Christoph Lameter
2006-11-30 19:33 ` Peter Zijlstra
2006-11-30 19:33 ` Peter Zijlstra
2006-12-01 11:28 ` Peter Zijlstra
2006-12-01 11:28 ` Peter Zijlstra
2006-11-30 19:02 ` Peter Zijlstra
2006-11-30 19:02 ` Peter Zijlstra
2006-11-30 19:37 ` Christoph Lameter
2006-11-30 19:37 ` Christoph Lameter
2006-11-30 19:40 ` Peter Zijlstra
2006-11-30 19:40 ` Peter Zijlstra
2006-11-30 20:11 ` Christoph Lameter
2006-11-30 20:11 ` Christoph Lameter
2006-11-30 20:15 ` Peter Zijlstra
2006-11-30 20:15 ` Peter Zijlstra
2006-11-30 20:29 ` Christoph Lameter
2006-11-30 20:29 ` Christoph Lameter
2006-11-30 10:14 ` [RFC][PATCH 2/6] mm: allow PF_MEMALLOC from softirq context Peter Zijlstra
2006-11-30 10:14 ` [RFC][PATCH 3/6] mm: serialize access to min_free_kbytes Peter Zijlstra
2006-11-30 10:14 ` [RFC][PATCH 4/6] mm: emergency pool and __GFP_EMERGENCY Peter Zijlstra
2006-11-30 10:14 ` [RFC][PATCH 5/6] slab: kmem_cache_objs_to_pages() Peter Zijlstra
2006-11-30 18:55 ` Christoph Lameter
2006-11-30 18:55 ` Christoph Lameter
2006-11-30 18:55 ` Peter Zijlstra
2006-11-30 18:55 ` Peter Zijlstra
2006-11-30 19:06 ` Christoph Lameter
2006-11-30 19:06 ` Christoph Lameter
2006-11-30 19:03 ` Peter Zijlstra [this message]
2006-11-30 19:03 ` Peter Zijlstra
2006-12-01 12:14 ` Peter Zijlstra
2006-12-01 12:14 ` Peter Zijlstra
2006-11-30 10:14 ` [RFC][PATCH 6/6] net: vm deadlock avoidance core Peter Zijlstra
2006-11-30 12:04 ` Peter Zijlstra
2006-11-30 12:04 ` Peter Zijlstra
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=1164913399.6588.158.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=clameter@sgi.com \
--cc=davem@davemloft.net \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.