linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan.kim@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	apw@canonical.com, riel@redhat.com, mel@csn.ul.ie,
	Lee Schermerhorn <lee.schermerhorn@hp.com>
Subject: Re: [PATCH 2/3] check unevictable flag in lumy reclaim v2
Date: Thu, 11 Jun 2009 20:59:28 +0900	[thread overview]
Message-ID: <28c262360906110459s923d7a6p4e555344e8bbd265@mail.gmail.com> (raw)
In-Reply-To: <9d4a7c0691aa5e13247f694f2dfe55ad.squirrel@webmail-b.css.fujitsu.com>

2009/6/11 KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>:
> Minchan Kim さん wrote:
>> On Thu, Jun 11, 2009 at 5:38 PM, KAMEZAWA
>> Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com> wrote:
>>> How about this ?
>>>
>>> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>>>
>>> Lumpy reclaim check pages from their pfn. Then, it can find unevictable
>>> pages
>>> in its loop.
>>> Abort lumpy reclaim when we find Unevictable page, we never get a lump
>>> of pages for requested order.
>>>
>>> Changelog: v1->v2
>>> ?- rewrote commet.
>>>
>>> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>>> ---
>>> ?mm/vmscan.c | ? ?9 +++++++++
>>> ?1 file changed, 9 insertions(+)
>>>
>>> Index: lumpy-reclaim-trial/mm/vmscan.c
>>> ===================================================================
>>> --- lumpy-reclaim-trial.orig/mm/vmscan.c
>>> +++ lumpy-reclaim-trial/mm/vmscan.c
>>> @@ -936,6 +936,15 @@ static unsigned long isolate_lru_pages(u
>>> ? ? ? ? ? ? ? ? ? ? ? ?/* Check that we have not crossed a zone
>>> boundary. */
>>> ? ? ? ? ? ? ? ? ? ? ? ?if (unlikely(page_zone_id(cursor_page) !=
>>> zone_id))
>>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?continue;
>>> + ? ? ? ? ? ? ? ? ? ? ? /*
>>> + ? ? ? ? ? ? ? ? ? ? ? ?* We tries to free all pages in this range to
>>> create
>>> + ? ? ? ? ? ? ? ? ? ? ? ?* a free large page. Then, if the range
>>> includes a page
>>> + ? ? ? ? ? ? ? ? ? ? ? ?* never be reclaimed, we have no reason to do
>>> more.
>>> + ? ? ? ? ? ? ? ? ? ? ? ?* PageUnevictable page is not a page which can
>>> be
>>> + ? ? ? ? ? ? ? ? ? ? ? ?* easily freed. Abort this scan now.
>>> + ? ? ? ? ? ? ? ? ? ? ? ?*/
>>> + ? ? ? ? ? ? ? ? ? ? ? if (unlikely(PageUnevictable(cursor_page)))
>>> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? break;
>>
>> __isolate_lru_pages already checked PageUnevictable to return error.
>> I want to remove repeated check although it is trivial.
>>
>> By your patch, It seems to remove PageUnevictable check in
>> __isolate_lru_pages.
>>
> yes.
>
>> But I know that. If we remove PageUnevictable check in
>> __isolate_lru_pages, it can't go into BUG in non-lumpy case. ( I
>> mentioned following as code)
>>
> In non-lumpy case, we'll never see Unevictable, maybe.

I think so if it doesn't happen RAM failure.
AFAIK, Unevictable check didn't related with RAM failure.

>
>>                 case -EBUSY:
>>                         /* else it is being freed elsewhere */
>>                         list_move(&page->lru, src);
>>                         continue;
>>
>>                 default:
>>                         BUG();
>>                 }
>>
>>
>> It means we can remove BUG in non-lumpy case and then add BUG into
>> __isolate_lru_pages directly.
>>
>> If we can do it, we can remove unnecessary PageUnevictable check in
>> __isolate_lru_page.
>>
> Hmm, but Unevicable check had tons of troubles at its implementation
> and I don't want to do it at once.

I think it's not a big problem.
As comment said, the check's goal is to prevent in lumpy case.
        /*
         * When this function is being called for lumpy reclaim, we
         * initially look into all LRU pages, active, inactive and
         * unevictable; only give shrink_page_list evictable pages.
         */
        if (PageUnevictable(page))
                return ret;

So I think we can remove this check.

>> I am not sure this is right in case of memcg.
>>
> I think we don't see Unevictable in memcg's path if my memcg-lru code
> works as designed.
>
> I'll postpone this patch for a while until my brain works well.

If you have a concern about that, how about this ?
(This code will be hunk since gmail webserver always mangle. Pz,forgive me)
Also, we can CC original authors.

--- a/mm/vmscan.c
++ b/mm/vmscan.c
@@ -936,19 +936,20 @@ static unsigned long isolate_lru_pages(unsigned
long nr_to_scan,
                        /* Check that we have not crossed a zone boundary. */
                        if (unlikely(page_zone_id(cursor_page) != zone_id))
                                continue;
-                       switch (__isolate_lru_page(cursor_page, mode, file)) {
-                       case 0:
+                       if (__isolate_lru_page(cursor_page, mode, file) == 0) {
                                list_move(&cursor_page->lru, dst);
                                nr_taken++;
                                scan++;
-                               break;
-
-                       case -EBUSY:
-                               /* else it is being freed elsewhere */
-                               list_move(&cursor_page->lru, src);
-                       default:
-                               break;  /* ! on LRU or wrong list */
                        }
+                       else if (PageUnevictable(cursor_page))
+                                       /*
+                                * We tries to free all pages in this
range to create
+                                * a free large page. Then, if the
range includes a page
+                                * never be reclaimed, we have no
reason to do more.
+                                * PageUnevictable page is not a page
which can be
+                                * easily freed. Abort this scan now.
+                                */
+                               break
                }
        }


> Thanks,
> -Kame
>
>



-- 
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>

  reply	other threads:[~2009-06-11 11:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  7:55 [PATCH 0/3] misc fix around vmscan/isolate_lru_pages KAMEZAWA Hiroyuki
2009-06-11  8:00 ` [PATCH 1/3] remove wrong rotation at lumpy reclaim KAMEZAWA Hiroyuki
2009-06-11  8:21   ` KOSAKI Motohiro
2009-06-11  9:18   ` Minchan Kim
2009-06-11 11:13     ` KAMEZAWA Hiroyuki
2009-06-11 11:20       ` Minchan Kim
2009-06-11 22:52     ` Minchan Kim
2009-06-11 15:06   ` Mel Gorman
2009-06-11  8:01 ` [PATCH 2/3] check unevictable flag in lumy reclaim KAMEZAWA Hiroyuki
2009-06-11  8:24   ` KOSAKI Motohiro
2009-06-11  8:38     ` [PATCH 2/3] check unevictable flag in lumy reclaim v2 KAMEZAWA Hiroyuki
2009-06-11  8:44       ` KOSAKI Motohiro
2009-06-11  9:37       ` Minchan Kim
2009-06-11  9:39         ` Minchan Kim
2009-06-11 11:19         ` KAMEZAWA Hiroyuki
2009-06-11 11:59           ` Minchan Kim [this message]
2009-06-11 12:18             ` KAMEZAWA Hiroyuki
2009-06-11 22:55               ` Minchan Kim
2009-06-11 15:07   ` [PATCH 2/3] check unevictable flag in lumy reclaim Mel Gorman
2009-06-11  8:04 ` [PATCH 3/3] memcg: fix LRU rotation of isolate_lru_pages with memcg KAMEZAWA Hiroyuki

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=28c262360906110459s923d7a6p4e555344e8bbd265@mail.gmail.com \
    --to=minchan.kim@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --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;
as well as URLs for NNTP newsgroup(s).