All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: 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: Tue, 15 Jan 2008 12:46:29 +0000	[thread overview]
Message-ID: <478CAB25.30300@grupopie.com> (raw)
In-Reply-To: <20080115100450.1180.KOSAKI.MOTOHIRO@jp.fujitsu.com>

KOSAKI Motohiro wrote:
> Hi
> 
> at one point, I found the large file copy speed was different depending on
> the copy method.
> 
> I compared below method
>  - read(2) and write(2).
>  - mmap(2) x2 and memcpy.
>  - mmap(2) and write(2).
> 
> in addition, effect of fadvice(2) and madvice(2) is checked.
> 
> to a strange thing, 
>    - most faster method is read + write + fadvice.
>    - worst method is mmap + memcpy.

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.

Just my 2 cents,

-- 
Paulo Marques - www.grupopie.com

"All I ask is a chance to prove that money can't make me happy."

WARNING: multiple messages have this Message-ID (diff)
From: Paulo Marques <pmarques@grupopie.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: 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: Tue, 15 Jan 2008 12:46:29 +0000	[thread overview]
Message-ID: <478CAB25.30300@grupopie.com> (raw)
In-Reply-To: <20080115100450.1180.KOSAKI.MOTOHIRO@jp.fujitsu.com>

KOSAKI Motohiro wrote:
> Hi
> 
> at one point, I found the large file copy speed was different depending on
> the copy method.
> 
> I compared below method
>  - read(2) and write(2).
>  - mmap(2) x2 and memcpy.
>  - mmap(2) and write(2).
> 
> in addition, effect of fadvice(2) and madvice(2) is checked.
> 
> to a strange thing, 
>    - most faster method is read + write + fadvice.
>    - worst method is mmap + memcpy.

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.

Just my 2 cents,

-- 
Paulo Marques - www.grupopie.com

"All I ask is a chance to prove that money can't make me happy."

--
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:[~2008-01-15 12:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15  1:45 [RFC] mmaped copy too slow? KOSAKI Motohiro
2008-01-15  2:15 ` Rik van Riel
2008-01-15  2:15   ` Rik van Riel
2008-01-15  3:20   ` KOSAKI Motohiro
2008-01-15  3:20     ` KOSAKI Motohiro
2008-01-15  8:57     ` Peter Zijlstra
2008-01-15  8:57       ` Peter Zijlstra
2008-01-15  9:03       ` KOSAKI Motohiro
2008-01-15  9:03         ` KOSAKI Motohiro
2008-01-15  9:08         ` Peter Zijlstra
2008-01-15  9:08           ` Peter Zijlstra
2008-01-15 12:46 ` Paulo Marques [this message]
2008-01-15 12:46   ` Paulo Marques
2008-01-16  2:05   ` KOSAKI Motohiro
2008-01-16  2:05     ` KOSAKI Motohiro
2008-01-17  3:23     ` KOSAKI Motohiro
2008-01-17  3:23       ` KOSAKI Motohiro

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=478CAB25.30300@grupopie.com \
    --to=pmarques@grupopie.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 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.