From: "MinChan Kim" <minchan.kim@gmail.com>
To: Rik van Riel <riel@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [resend][PATCH -mm] split_lru: fix pagevec_move_tail() doesn't treat unevictable page
Date: Wed, 2 Jul 2008 09:39:15 +0900 [thread overview]
Message-ID: <28c262360807011739w5668920buf7880de6ed30f912@mail.gmail.com> (raw)
In-Reply-To: <20080701093840.07b48ced@bree.surriel.com>
Hi, Rik and Kosaki-san
I want to know exact race situation for remaining git log.
As you know, git log is important for me who is newbie to understand source
There are many possibility in this race problem.
Did you use hugepage in this test ?
I think that If you used hugepage, it seems to happen following race.
--------------
CPU1 CPU2
shm_unlock
scan_mapping_unevictable_pages
check_move_unevictable_page
ClearPageUnevictable rotate_reclaimable_page
PageUnevictable(page) return 0
SetPageUnevictable
list_move(LRU_UNEVICTABLE)
local_irq_save
pagevec_move_tail
Do you think it is possible ?
On Tue, Jul 1, 2008 at 10:38 PM, Rik van Riel <riel@redhat.com> wrote:
> On Tue, 01 Jul 2008 17:26:51 +0900
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>
>> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>
> Acked-by: Rik van Riel <riel@redhat.com>
>
> Good catch!
>
>> @@ -116,7 +116,7 @@ static void pagevec_move_tail(struct pag
>> zone = pagezone;
>> spin_lock(&zone->lru_lock);
>> }
>> - if (PageLRU(page) && !PageActive(page)) {
>> + if (PageLRU(page) && !PageActive(page) && !PageUnevictable(page)) {
>> int lru = page_is_file_cache(page);
>> list_move_tail(&page->lru, &zone->lru[lru].list);
>> pgmoved++;
>
> --
> All rights reversed.
>
--
Kinds regards,
MinChan Kim
--
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:[~2008-07-02 0:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 7:01 [PATCH " KOSAKI Motohiro
2008-07-01 7:34 ` MinChan Kim
2008-07-01 7:56 ` KOSAKI Motohiro
2008-07-01 8:16 ` MinChan Kim
2008-07-01 8:26 ` [resend][PATCH " KOSAKI Motohiro
2008-07-01 13:38 ` Rik van Riel
2008-07-02 0:39 ` MinChan Kim [this message]
2008-07-02 0:49 ` MinChan Kim
2008-07-02 0:54 ` MinChan Kim
2008-07-02 3:30 ` KOSAKI Motohiro
2008-07-02 5:00 ` MinChan 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=28c262360807011739w5668920buf7880de6ed30f912@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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