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: Mel Gorman <mel@csn.ul.ie>,
	NARAYANAN GOPALAKRISHNAN <narayanan.g@samsung.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"cl@linux-foundation.org" <cl@linux-foundation.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: Performance degradation seen after using one list for hot/cold pages.
Date: Thu, 25 Jun 2009 18:11:12 +0900	[thread overview]
Message-ID: <28c262360906250211p4f5d8b30q156a06d97ddb7da7@mail.gmail.com> (raw)
In-Reply-To: <20090623090630.f06b7b17.kamezawa.hiroyu@jp.fujitsu.com>

On Tue, Jun 23, 2009 at 9:06 AM, KAMEZAWA
Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Mon, 22 Jun 2009 17:52:36 +0100
> Mel Gorman <mel@csn.ul.ie> wrote:
>
>> On Mon, Jun 22, 2009 at 11:32:03AM +0000, NARAYANAN GOPALAKRISHNAN wrote:
>> > Hi,
>> >
>> > We are running on VFAT.
>> > We are using iozone performance benchmarking tool (http://www.iozone.org/src/current/iozone3_326.tar) for testing.
>> >
>> > The parameters are
>> > /iozone -A -s10M -e -U /tmp -f /tmp/iozone_file
>> >
>> > Our block driver requires requests to be merged to get the best performance.
>> > This was not happening due to non-contiguous pages in all kernels >= 2.6.25.
>> >
>>
>> Ok, by the looks of things, all the aio_read() requests are due to readahead
>> as opposed to explicit AIO  requests from userspace. In this case, nothing
>> springs to mind that would avoid excessive requests for cold pages.
>>
>> It looks like the simpliest solution is to go with the patch I posted.
>> Does anyone see a better alternative that doesn't branch in rmqueue_bulk()
>> or add back the hot/cold PCP lists?
>>
> No objection.  But 2 questions...
>
>> -        list_add(&page->lru, list);
>> +        if (likely(cold == 0))
>> +            list_add(&page->lru, list);
>> +        else
>> +            list_add_tail(&page->lru, list);
>>          set_page_private(page, migratetype);
>>          list = &page->lru;
>>      }
>
> 1. if (likely(coild == 0))
>        "likely" is necessary ?
>
> 2. Why moving pointer "list" rather than following ?
>
>        if (cold)
>                list_add(&page->lru, list);
>        else
>                list_add_tail(&page->lru, list);


I agree.
We can remove unnecessary list head moving forward.


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

  parent reply	other threads:[~2009-06-25  9:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 11:32 Re: Re: Performance degradation seen after using one list for hot/cold pages NARAYANAN GOPALAKRISHNAN
2009-06-22 16:52 ` Mel Gorman
2009-06-23  0:06   ` KAMEZAWA Hiroyuki
2009-06-23 17:41     ` Christoph Lameter
2009-06-25  9:11     ` Minchan Kim [this message]
2009-06-29  9:15     ` Mel Gorman
2009-07-08  2:37       ` Performance degradation seen after using one list for hot/coldpages Narayanan Gopalakrishnan
2009-07-08 14:53         ` Christoph Lameter
2009-07-08 15:27           ` Mel Gorman
2009-07-08 21:32             ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2009-06-22  5:50 Performance degradation seen after using one list for hot/cold pages Narayanan Gopalakrishnan
2009-06-22  7:41 ` KAMEZAWA Hiroyuki
2009-06-22 10:06   ` Mel Gorman
2009-07-08 21:29     ` 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=28c262360906250211p4f5d8b30q156a06d97ddb7da7@mail.gmail.com \
    --to=minchan.kim@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=narayanan.g@samsung.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).