From: David Rientjes <rientjes@google.com>
To: Dan Smith <danms@us.ibm.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Ensure that walk_page_range()'s start and end are page-aligned
Date: Mon, 13 Feb 2012 13:55:31 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1202131350500.17296@chino.kir.corp.google.com> (raw)
In-Reply-To: <87zkcm23az.fsf@caffeine.danplanet.com>
On Mon, 13 Feb 2012, Dan Smith wrote:
> DR> It doesn't "ensure" anything without CONFIG_DEBUG_VM enabled, which
> DR> isn't the default.
>
> Are you proposing a change in verbiage or a stronger check? A
> VM_BUG_ON() seemed on par with other checks, such as the one in
> get_user_pages_fast().
>
That's not a precedent, there's a big difference between the performance
of gup_fast(), where we can't spare an additional compare and branch, and
walk_page_range(). VM_BUG_ON() is typically used in situations where a
debug kernel has been built, including CONFIG_DEBUG_VM, and the check
helps to isolate a problem that would be otherwise difficult to find. If
that fits the criteria, fine, but it doesn't "ensure" walk_page_range()
always has start and end addresses that are page aligned, so the changelog
needs to be modified to describe why an error in this path wouldn't be
evident.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-02-13 21:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 19:39 Dan Smith
2012-02-10 19:45 ` Michal Nazarewicz
2012-02-10 19:57 ` Dan Smith
2012-02-10 20:13 ` Michal Nazarewicz
2012-02-13 10:12 ` David Rientjes
2012-02-13 14:52 ` Dan Smith
2012-02-13 21:55 ` David Rientjes [this message]
2012-02-14 14:59 ` Dan Smith
2012-02-14 21:04 ` David Rientjes
2012-02-15 14:39 ` Dan Smith
2012-02-24 19:19 ` Dan Smith
2012-02-24 20:55 ` Andrew Morton
2012-02-24 21:03 ` Dan Smith
-- strict thread matches above, loose matches on Subject: below --
2012-02-10 15:53 Dan Smith
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.DEB.2.00.1202131350500.17296@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=danms@us.ibm.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