From: Pekka Enberg <penberg@kernel.org>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Christoph Lameter <cl@linux.com>, Matt Mackall <mpm@selenic.com>,
Glauber Costa <glommer@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>,
Joonsoo Kim <js1304@gmail.com>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] mm/slab: Fix drain freelist excessively
Date: Sun, 07 Jul 2013 18:38:44 +0300 [thread overview]
Message-ID: <51D98B84.4000607@kernel.org> (raw)
In-Reply-To: <20130707092448.GA11177@hacker.(null)>
On 7/7/13 12:24 PM, Wanpeng Li wrote:
> On Fri, Jul 05, 2013 at 01:37:28PM +0000, Christoph Lameter wrote:
>> On Thu, 4 Jul 2013, Wanpeng Li wrote:
>>
>>> This patch fix the callers that pass # of objects. Make sure they pass #
>>> of slabs.
>>
>> Acked-by: Christoph Lameter <cl@linux.com>
>
> Hi Pekka,
>
> Is it ok for you to pick this patchset? ;-)
Applied, thanks a lot!
--
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: Pekka Enberg <penberg@kernel.org>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Christoph Lameter <cl@linux.com>, Matt Mackall <mpm@selenic.com>,
Glauber Costa <glommer@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>,
Joonsoo Kim <js1304@gmail.com>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] mm/slab: Fix drain freelist excessively
Date: Sun, 07 Jul 2013 18:38:44 +0300 [thread overview]
Message-ID: <51D98B84.4000607@kernel.org> (raw)
In-Reply-To: <20130707092448.GA11177@hacker.(null)>
On 7/7/13 12:24 PM, Wanpeng Li wrote:
> On Fri, Jul 05, 2013 at 01:37:28PM +0000, Christoph Lameter wrote:
>> On Thu, 4 Jul 2013, Wanpeng Li wrote:
>>
>>> This patch fix the callers that pass # of objects. Make sure they pass #
>>> of slabs.
>>
>> Acked-by: Christoph Lameter <cl@linux.com>
>
> Hi Pekka,
>
> Is it ok for you to pick this patchset? ;-)
Applied, thanks a lot!
next prev parent reply other threads:[~2013-07-07 15:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 0:33 [PATCH v3 1/5] mm/slab: Fix drain freelist excessively Wanpeng Li
2013-07-04 0:33 ` Wanpeng Li
2013-07-04 0:33 ` [PATCH v3 2/5] mm/slab: Sharing s_next and s_stop between slab and slub Wanpeng Li
2013-07-04 0:33 ` Wanpeng Li
2013-07-04 0:33 ` [PATCH v3 3/5] mm/slab: Fix /proc/slabinfo unwriteable for slab Wanpeng Li
2013-07-04 0:33 ` Wanpeng Li
2013-07-04 0:33 ` [PATCH v3 4/5] mm/slub: Drop unnecessary nr_partials Wanpeng Li
2013-07-04 0:33 ` Wanpeng Li
2013-07-04 0:33 ` [PATCH v3 5/5] mm/slub: Use node_nr_slabs and node_nr_objs in get_slabinfo Wanpeng Li
2013-07-04 0:33 ` Wanpeng Li
2013-07-05 13:37 ` [PATCH v3 1/5] mm/slab: Fix drain freelist excessively Christoph Lameter
2013-07-05 13:37 ` Christoph Lameter
2013-07-07 9:24 ` Wanpeng Li
2013-07-07 15:38 ` Pekka Enberg [this message]
2013-07-07 15:38 ` Pekka Enberg
2013-07-07 9:24 ` Wanpeng Li
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=51D98B84.4000607@kernel.org \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=glommer@parallels.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=mpm@selenic.com \
--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 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.