From: Alexander Duyck <alexander.duyck@gmail.com>
To: Wei Yang <richard.weiyang@linux.alibaba.com>
Cc: Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
David Hildenbrand <david@redhat.com>
Subject: Re: [Patch v2] mm/page_reporting: drop stale list head check in page_reporting_cycle
Date: Tue, 18 Aug 2020 07:55:28 -0700 [thread overview]
Message-ID: <CAKgT0UfQ4BGygD-r+uVpMhF2RBAynhZp54H-6EVrEc7PdESNqQ@mail.gmail.com> (raw)
In-Reply-To: <20200818084448.33969-1-richard.weiyang@linux.alibaba.com>
On Tue, Aug 18, 2020 at 1:45 AM Wei Yang
<richard.weiyang@linux.alibaba.com> wrote:
>
> list_for_each_entry_safe() guarantees that we will never stumble over
> the list head; "&page->lru != list" will always evaluate to true. Let's
> simplify.
>
> Signed-off-by: Wei Yang <richard.weiyang@linux.alibaba.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> ---
> mm/page_reporting.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/page_reporting.c b/mm/page_reporting.c
> index 3bbd471cfc81..aaaa3605123d 100644
> --- a/mm/page_reporting.c
> +++ b/mm/page_reporting.c
> @@ -178,7 +178,7 @@ page_reporting_cycle(struct page_reporting_dev_info *prdev, struct zone *zone,
> * the new head of the free list before we release the
> * zone lock.
> */
> - if (&page->lru != list && !list_is_first(&page->lru, list))
> + if (!list_is_first(&page->lru, list))
> list_rotate_to_front(&page->lru, list);
>
> /* release lock before waiting on report processing */
Reviewed-by: Alexander Duyck <alexander.h.duyck@linux.intel.com>
prev parent reply other threads:[~2020-08-18 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 8:44 Wei Yang
2020-08-18 9:09 ` Wei Yang
2020-08-18 14:55 ` Alexander Duyck [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=CAKgT0UfQ4BGygD-r+uVpMhF2RBAynhZp54H-6EVrEc7PdESNqQ@mail.gmail.com \
--to=alexander.duyck@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@linux.alibaba.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