From: Bob Liu <lliubbo@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, kosaki.motohiro@jp.fujitsu.com
Subject: Re: [RESEND][PATCH] __isolate_lru_page:skip unneeded "not"
Date: Sat, 3 Apr 2010 06:25:08 +0800 [thread overview]
Message-ID: <y2tcf18f8341004021525wa44a76ev8f4372a7191e0240@mail.gmail.com> (raw)
In-Reply-To: <20100402150511.6f71fbfd.akpm@linux-foundation.org>
On 4/3/10, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 1 Apr 2010 21:37:35 +0800
> Bob Liu <lliubbo@gmail.com> wrote:
>
>> PageActive(page) will return int 0 or 1, mode is also int 0 or 1,
>> they are comparible so "not" is unneeded to be sure to boolean
>> values.
>> I also collected the ISOLATE_BOTH check together.
>>
>> Signed-off-by: Bob Liu <lliubbo@gmail.com>
>> ---
>> mm/vmscan.c | 15 +++++----------
>> 1 files changed, 5 insertions(+), 10 deletions(-)
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index e0e5f15..ce9ee85 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -862,16 +862,11 @@ int __isolate_lru_page(struct page *page, int mode,
>> int file)
>> if (!PageLRU(page))
>> return ret;
>>
>> - /*
>> - * When checking the active state, we need to be sure we are
>> - * dealing with comparible boolean values. Take the logical not
>> - * of each.
>> - */
>
> You deleted a spelling mistake too!
>
>> - if (mode != ISOLATE_BOTH && (!PageActive(page) != !mode))
>> - return ret;
>> -
>> - if (mode != ISOLATE_BOTH && page_is_file_cache(page) != file)
>> - return ret;
>> + if (mode != ISOLATE_BOTH) {
>> + if ((PageActive(page) != mode) ||
>> + (page_is_file_cache(page) != file))
>> + return ret;
>> + }
>
> The compiler should be able to avoid testing for ISOLATE_BOTH twice,
Thanks for your kindly reply.
then is the two "not" able to avoid by the compiler ?
if yes, this patch is meanless and should be ignore.
> and I think the previous code layout was superior:
>
> if (mode != ISOLATE_BOTH && (!PageActive(page) != !mode))
> return ret;
>
> if (mode != ISOLATE_BOTH && page_is_file_cache(page) != file)
> return ret;
>
> Because it gives us nice places to put a comment explaining what the
> code is doing, whereas making it a more complex single expression:
>
> if (mode != ISOLATE_BOTH) {
> if ((PageActive(page) != mode) ||
> (page_is_file_cache(page) != file))
> return ret;
> }
>
> makes clearly commenting each test more difficult.
>
> Yeah, there's no comment there at present. But that's because we suck
> - I'm sure someone is working on it ;)
>
>
--
Regards,
--Bob
--
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:[~2010-04-02 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 13:37 [RESEND][PATCH] __isolate_lru_page:skip unneeded "not" Bob Liu
2010-04-02 22:05 ` Andrew Morton
2010-04-02 22:25 ` Bob Liu [this message]
2010-04-02 23:01 ` Andrew Morton
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=y2tcf18f8341004021525wa44a76ev8f4372a7191e0240@mail.gmail.com \
--to=lliubbo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).