All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@saeurebad.de>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	npiggin@suse.de, riel@redhat.com, linux-mm@kvack.org
Subject: Re: [patch] mm: more likely reclaim MADV_SEQUENTIAL mappings II
Date: Wed, 22 Oct 2008 09:15:14 +0200	[thread overview]
Message-ID: <87abcxksn1.fsf@saeurebad.de> (raw)
In-Reply-To: <20081022152911.1CD9.KOSAKI.MOTOHIRO@jp.fujitsu.com> (KOSAKI Motohiro's message of "Wed, 22 Oct 2008 15:39:41 +0900 (JST)")

KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> writes:

>> >> Is http://hannes.saeurebad.de/madvseq/ still true with this version?
>> >
>> > No, sorry, still running benchmarks on this version.  Coming up
>> > soon...
>> 
>> Ok, reran the tests I used for the data on this website and updated it.
>> Take a look.  I am quite overwhelmed by the results, hehe.
>> 
>> Kosaki-san, could you perhaps run the tests you did for the previous
>> patch on this one, too?  I am not getting any stable results for
>> throughput measuring...
>
> Usually, any reclaim throughput mesurement isn't stable.
> Then I used an average of five times mesurement.

Ah, okay.  I will give it another spin, too.

> Unfortunately, I can't understand I should mesure which patch combination
> because you and Nick post many patches of this issue related yesterday.
> Please let me know it?

mmotm
- the old mm-more-likely-reclaim-madv_sequential-mappings
+ Nick's mm: dont mark_page_accessed in fault path (from yesterday)
+ Apply this patch

Andrew's tree (not yet released) already has the first two changes, so
if he releases a new mmotm in the meantime, you only need this patch on
top of it.

        Hannes

--
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:[~2008-10-22  7:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 10:32 [rfc] mm: more likely reclaim MADV_SEQUENTIAL mappings Johannes Weiner
2008-10-21 10:43 ` Nick Piggin
2008-10-21 11:33   ` [patch] mm: more likely reclaim MADV_SEQUENTIAL mappings II Johannes Weiner
2008-10-21 22:13     ` Andrew Morton
2008-10-22  0:09       ` Johannes Weiner
2008-10-22  0:51         ` Johannes Weiner
2008-10-22  6:39           ` KOSAKI Motohiro
2008-10-22  7:15             ` Johannes Weiner [this message]
2008-10-22  7:41               ` Andrew Morton
2008-10-24  0:21     ` Johannes Weiner
2008-10-24 12:55       ` KOSAKI Motohiro
2008-10-24 14:02         ` Johannes Weiner
2008-10-24 14:31         ` Rik van Riel
2008-10-24 16:15           ` Johannes Weiner
2008-10-24 23:48             ` Johannes Weiner
2008-10-24 18:59           ` KOSAKI Motohiro
2008-10-21 14:40 ` [rfc] mm: more likely reclaim MADV_SEQUENTIAL mappings Rik van Riel
2008-10-21 15:20   ` Johannes Weiner

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=87abcxksn1.fsf@saeurebad.de \
    --to=hannes@saeurebad.de \
    --cc=akpm@linux-foundation.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.