linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Joonsoo Kim <js1304@gmail.com>,
	Glauber Costa <glommer@parallels.com>,
	linux-mm@kvack.org, David Rientjes <rientjes@google.com>
Subject: Re: [3.11 1/4] slub: Make cpu partial slab support configurable V2
Date: Tue, 18 Jun 2013 09:35:13 +0300	[thread overview]
Message-ID: <51BFFFA1.8030402@kernel.org> (raw)
In-Reply-To: <0000013f44418a14-7abe9784-a481-4c34-8ff3-c3afe2d57979-000000@email.amazonses.com>

On 06/14/2013 10:55 PM, Christoph Lameter wrote:
> cpu partial support can introduce level of indeterminism that is not wanted
> in certain context (like a realtime kernel). Make it configurable.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>

The changelog is way too vague. Numbers? Anyone who would want to
use this in real world scenarios, please speak up!

			Pekka

--
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>

  reply	other threads:[~2013-06-18  6:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130614195500.373711648@linux.com>
2013-06-14 19:55 ` [3.11 2/4] slob: Rework #ifdeffery in slab.h Christoph Lameter
2013-06-14 19:55 ` [3.11 1/4] slub: Make cpu partial slab support configurable V2 Christoph Lameter
2013-06-18  6:35   ` Pekka Enberg [this message]
2013-06-18 14:17     ` Christoph Lameter
2013-06-18 15:21       ` Clark Williams
2013-06-18 15:25         ` Pekka Enberg
2013-06-25 14:24           ` Steven Rostedt
2013-07-01 18:16             ` Christoph Lameter
2013-07-02 15:09               ` Clark Williams
2013-07-02 16:47                 ` Christoph Lameter
2013-07-02 16:53                   ` Clark Williams
2013-07-17  2:46                   ` Steven Rostedt
2013-07-17  7:04                     ` Pekka Enberg
2013-07-17 12:23                       ` Steven Rostedt
2013-07-17 15:04                         ` Christoph Lameter
2013-07-17 15:15                           ` Steven Rostedt
2013-07-17 15:24                             ` Steven Rostedt
2013-06-19  5:22   ` Joonsoo Kim
2013-06-19 14:29     ` Christoph Lameter
2013-06-20  1:50       ` Joonsoo Kim
2013-06-20  2:53         ` Wanpeng Li
2013-06-20  2:53         ` Wanpeng Li
     [not found]         ` <51c26ebd.e842320a.5dc1.ffffedfcSMTPIN_ADDED_BROKEN@mx.google.com>
2013-06-20  5:45           ` Joonsoo Kim
2013-06-20  5:50         ` Joonsoo Kim
2013-07-07 16:10           ` Pekka Enberg
2013-06-14 20:06 ` [3.11 3/4] Move kmalloc_node functions to common code Christoph Lameter
2013-06-18 15:38   ` Pekka Enberg
2013-06-18 17:02     ` Christoph Lameter
2013-07-07 16:14       ` Pekka Enberg
2013-07-08 18:55         ` Christoph Lameter
2013-06-19  6:30   ` Joonsoo Kim
2013-06-19 14:33     ` Christoph Lameter
2013-06-20  1:51       ` Joonsoo Kim
2013-06-14 20:06 ` [3.11 4/4] Move kmalloc definitions to slab.h 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=51BFFFA1.8030402@kernel.org \
    --to=penberg@kernel.org \
    --cc=cl@linux.com \
    --cc=glommer@parallels.com \
    --cc=js1304@gmail.com \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).