linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ezequiel Garcia <elezegarcia@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	JoonSoo Kim <js1304@gmail.com>, Tim Bird <tim.bird@am.sony.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	David Rientjes <rientjes@google.com>,
	Glauber Costa <glommer@parallels.com>
Subject: Re: [PATCH v2 0/10] mm: SLxB cleaning and trace accuracy improvement
Date: Sat, 8 Sep 2012 19:45:51 -0300	[thread overview]
Message-ID: <CALF0-+U=sFgynE__V-XTN1SAgJHV_3VigRrdxuXFinbiWPg2oQ@mail.gmail.com> (raw)
In-Reply-To: <00000139a801aba3-4616277c-d845-4b62-83ec-1a1950b05751-000000@email.amazonses.com>

Christoph,

On Sat, Sep 8, 2012 at 7:30 PM, Christoph Lameter <cl@linux.com> wrote:
> On Sat, 8 Sep 2012, Ezequiel Garcia wrote:
>
>> This is the second spin of my patchset to clean SLxB and improve kmem
>> trace events accuracy.
>
> Please redo the patches on top of the patchsets that create
> mm/slab_common.c. You will be able to extract a lot more common code and
> help the goal of having as much common code as possible. PLease move as
> much as possible of the common functions into slab_common.c
>

Ah, I wasn't sure where to base my patches. I can split this patchset in two and
base the SLAB/SLUB commonize part on top of your tree, or perhaps just
based everything on top of your tree.

Is it this one?
http://west.gentwo.org/gitweb/?p=christoph;a=shortlog;h=refs/heads/common

I have to admit I started thinking of this commonization after seeing
your common
code patches.

Thanks!
Ezequiel.

  reply	other threads:[~2012-09-08 22:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08 20:49 [PATCH v2 0/10] mm: SLxB cleaning and trace accuracy improvement Ezequiel Garcia
2012-09-08 22:30 ` Christoph Lameter
2012-09-08 22:45   ` Ezequiel Garcia [this message]
2012-09-08 23:28     ` Christoph
2012-09-13  0:28 ` Ezequiel Garcia

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='CALF0-+U=sFgynE__V-XTN1SAgJHV_3VigRrdxuXFinbiWPg2oQ@mail.gmail.com' \
    --to=elezegarcia@gmail.com \
    --cc=cl@linux.com \
    --cc=glommer@parallels.com \
    --cc=js1304@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=rostedt@goodmis.org \
    --cc=tim.bird@am.sony.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).