From: Hugh Dickins <hughd@google.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: page_alloc: remove branch operation in free_pages_prepare()
Date: Thu, 7 Mar 2013 10:54:15 -0800 (PST) [thread overview]
Message-ID: <alpine.LNX.2.00.1303071050080.6087@eggly.anvils> (raw)
In-Reply-To: <1362644480-18381-1-git-send-email-iamjoonsoo.kim@lge.com>
On Thu, 7 Mar 2013, Joonsoo Kim wrote:
> When we found that the flag has a bit of PAGE_FLAGS_CHECK_AT_PREP,
> we reset the flag. If we always reset the flag, we can reduce one
> branch operation. So remove it.
>
> Cc: Hugh Dickins <hughd@google.com>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
I don't object to this patch. But certainly I would have written it
that way in order not to dirty a cacheline unnecessarily. It may be
obvious to you that the cacheline in question is almost always already
dirty, and the branch almost always more expensive. But I'll leave that
to you, and to those who know more about these subtle costs than I do.
Hugh
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 8fcced7..778f2a9 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -614,8 +614,7 @@ static inline int free_pages_check(struct page *page)
> return 1;
> }
> page_nid_reset_last(page);
> - if (page->flags & PAGE_FLAGS_CHECK_AT_PREP)
> - page->flags &= ~PAGE_FLAGS_CHECK_AT_PREP;
> + page->flags &= ~PAGE_FLAGS_CHECK_AT_PREP;
> return 0;
> }
>
--
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-03-07 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 8:21 Joonsoo Kim
2013-03-07 18:54 ` Hugh Dickins [this message]
2013-03-08 0:45 ` Joonsoo Kim
2013-03-08 2:01 ` Hugh Dickins
2013-03-09 3:54 ` Will Huck
2013-03-13 8:08 ` Joonsoo Kim
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=alpine.LNX.2.00.1303071050080.6087@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox