From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Paulo Marques <pmarques@grupopie.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] mmaped copy too slow?
Date: Thu, 17 Jan 2008 12:23:16 +0900 [thread overview]
Message-ID: <20080117121231.11D4.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20080116110200.11B4.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Hi
> > One thing you could also try is to pass MAP_POPULATE to mmap so that the
> > page tables are filled in at the time of the mmap, avoiding a lot of
> > page faults later.
> >
>
> OK, I will test your idea and report about tomorrow.
> but I don't think page fault is major performance impact.
I got more interesting result :)
MAP_POPULATE is harmful result at large copy.
1G copy
elapse(sec)
--------------------------------------------
mmap 71.54
mmap + madvice 69.63
mmap + populate 100.87
mmap + populate + madvice 101.16
more detail:
time command output of mmap copy
0.50user 3.59system 1:11.54elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
2101192inputs+2097160outputs (32776major+491573minor)pagefaults 0swaps
time command output of mmap+populate copy
0.53user 5.13system 1:40.87elapsed 5%CPU (0avgtext+0avgdata 0maxresident)k
4200808inputs+2097160outputs (49164major+737340minor)pagefaults 0swaps
input blocks increase about x2.
in fact, mmap(MAP_POPULATE) read disk to memory and drop it just after,
thus read again.
of cource, when copy file size is enough small, MAP_POPULATE is effective.
100M copy
elapse(sec)
--------------------------------------------
mmap 7.38
mmap + madvice 7.29
mmap + populate 7.13
mmap + populate + madvice 6.65
- kosaki
--
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>
prev parent reply other threads:[~2008-01-17 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 1:45 KOSAKI Motohiro
2008-01-15 2:15 ` Rik van Riel
2008-01-15 3:20 ` KOSAKI Motohiro
2008-01-15 8:57 ` Peter Zijlstra
2008-01-15 9:03 ` KOSAKI Motohiro
2008-01-15 9:08 ` Peter Zijlstra
2008-01-15 12:46 ` Paulo Marques
2008-01-16 2:05 ` KOSAKI Motohiro
2008-01-17 3:23 ` KOSAKI Motohiro [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=20080117121231.11D4.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pmarques@grupopie.com \
--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