From: Johannes Weiner <hannes@cmpxchg.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-mm@kvack.org
Subject: Re: [patch 1/4] mm: drop unneeded double negations
Date: Tue, 21 Jul 2009 13:18:02 +0200 [thread overview]
Message-ID: <20090721111802.GA9050@cmpxchg.org> (raw)
In-Reply-To: <20090721093312.GA25383@csn.ul.ie>
On Tue, Jul 21, 2009 at 10:33:13AM +0100, Mel Gorman wrote:
> On Tue, Jul 21, 2009 at 10:56:31AM +0200, Johannes Weiner wrote:
> > out_set_pte:
> > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > index 07fd8aa..46ec6a5 100644
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -516,7 +516,7 @@ int remove_mapping(struct address_space *mapping, struct page *page)
> > void putback_lru_page(struct page *page)
> > {
> > int lru;
> > - int active = !!TestClearPageActive(page);
> > + int active = TestClearPageActive(page);
> > int was_unevictable = PageUnevictable(page);
> >
>
> But are you *sure* about this change?
>
> active it used as an array offset later in this function for evictable pages
> so it needs to be 1 or 0 but IIRC, the TestClear functions are not guaranteed
> to return 0 or 1 on all architectures. They return 0 or non-zero. I'm 99.999%
> certain I've been bitten before by test_bit returning the word with the one
> bit set instead of 1. Maybe things have changed since or it's my
> imagination but can you double check please?
You are correct. I was a bit naive there and relied on the
documentation of the generic versions of test_and_clear_bit().
However,
- arm returns something non-zero for the atomic versions but
uses the true boolean generic unlocked versions
- ia64 seems to returns true boolean for everything but
__test_and_clear_bit
Everyone else returns true booleans, so I think these two should
adjusted.
Andrew, please ignore this patch for now, I will resend it once I
fixed arm and ia64.
Thanks for pointing it out, Mel.
Hannes
--
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>
prev parent reply other threads:[~2009-07-21 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 8:56 [patch 1/4] mm: drop unneeded double negations Johannes Weiner
2009-07-21 8:56 ` [patch 2/4] mm: introduce page_lru_type() Johannes Weiner
2009-07-22 1:52 ` Minchan Kim
2009-07-22 9:07 ` Johannes Weiner
2009-07-22 12:37 ` Minchan Kim
2009-07-22 16:01 ` Rik van Riel
2009-07-21 8:56 ` [patch 3/4] mm: return boolean from page_is_file_cache() Johannes Weiner
2009-07-21 8:56 ` [patch 4/4] mm: return boolean from page_has_private() Johannes Weiner
2009-07-22 16:49 ` Christoph Lameter
2009-07-22 17:50 ` Johannes Weiner
2009-07-22 17:54 ` [patch 5/4] mm: document is_page_cache_freeable() Johannes Weiner
2009-07-22 19:02 ` Christoph Lameter
2009-07-22 21:55 ` Li, Ming Chun
2009-07-22 22:10 ` Johannes Weiner
2009-07-22 23:51 ` Li, Ming Chun
2009-07-22 23:58 ` Christoph Lameter
2009-07-21 9:33 ` [patch 1/4] mm: drop unneeded double negations Mel Gorman
2009-07-21 11:18 ` Johannes Weiner [this message]
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=20090721111802.GA9050@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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).