From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: David Rientjes <rientjes@google.com>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm/page_alloc: remove repetitious local_irq_save() in __zone_pcp_update()
Date: Wed, 19 Jun 2013 16:21:58 -0700 [thread overview]
Message-ID: <51C23D16.3020805@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306191615240.17318@chino.kir.corp.google.com>
On 06/19/2013 04:17 PM, David Rientjes wrote:
> On Wed, 19 Jun 2013, Cody P Schafer wrote:
>
>> Re-examining this, I've realized that my previous patchset containing
>> "mm/page_alloc: convert zone_pcp_update() to rely on memory barriers
>> instead of stop_machine()"
>>
>> already went through and fixed this up (the right way). So ignore this patch.
>>
>
> If you're referring to
>
> mm-page_alloc-factor-out-setting-of-pcp-high-and-pcp-batch.patch
> mm-page_alloc-prevent-concurrent-updaters-of-pcp-batch-and-high.patch
> mm-page_alloc-insert-memory-barriers-to-allow-async-update-of-pcp-batch-and-high.patch
> mm-page_alloc-protect-pcp-batch-accesses-with-access_once.patch
> mm-page_alloc-convert-zone_pcp_update-to-rely-on-memory-barriers-instead-of-stop_machine.patch
> mm-page_alloc-when-handling-percpu_pagelist_fraction-dont-unneedly-recalulate-high.patch
> mm-page_alloc-factor-setup_pageset-into-pageset_init-and-pageset_set_batch.patch
> mm-page_alloc-relocate-comment-to-be-directly-above-code-it-refers-to.patch
> mm-page_alloc-factor-zone_pageset_init-out-of-setup_zone_pageset.patch
> mm-page_alloc-in-zone_pcp_update-uze-zone_pageset_init.patch
> mm-page_alloc-rename-setup_pagelist_highmark-to-match-naming-of-pageset_set_batch.patch
>
> from -mm then I'll review them separately because they have their own
> issues. Thanks.
>
I am. You may also want to note
mm-page_alloc-dont-re-init-pageset-in-zone_pcp_update.patch
which fixes a bug in that patchset.
--
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>
next prev parent reply other threads:[~2013-06-19 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 22:10 [PATCH] mm/page_alloc: remove repetitious local_irq_save() in __zone_pcp_update() Cody P Schafer
2013-06-19 9:15 ` Srivatsa S. Bhat
2013-06-19 22:53 ` David Rientjes
2013-06-19 23:06 ` Cody P Schafer
2013-06-19 23:17 ` David Rientjes
2013-06-19 23:21 ` Cody P Schafer [this message]
2013-06-20 6:32 ` Srivatsa S. Bhat
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=51C23D16.3020805@linux.vnet.ibm.com \
--to=cody@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=srivatsa.bhat@linux.vnet.ibm.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).