From: Voluspa <lista1@comhem.se>
To: Fengguang Wu <wfg@mail.ustc.edu.cn>
Cc: akpm@osdl.org, arjan@infradead.org, Valdis.Kletnieks@vt.edu,
diegocg@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] readahead: initial method - expected read size - fix fastcall
Date: Thu, 8 Jun 2006 10:28:02 +0200 [thread overview]
Message-ID: <20060608102802.6e07b148.lista1@comhem.se> (raw)
In-Reply-To: <349754431.09938@ustc.edu.cn>
On Thu, 8 Jun 2006 16:13:52 +0800 Fengguang Wu wrote:
> It's interesting that copying of sparse file is more efficient with small
> readahead size :) I get the same conclusion, though with smaller differences:
How on earth can you copy the file without overwriting the target /dev/null?
As you saw, I could just "cat" the file. Size was:
root:sleipner:~# dd if=/dev/zero of=sparse bs=1M seek=5000 count=1
1+0 records in
1+0 records out
root:sleipner:~# ls -l sparse
1040 -rw-r--r-- 1 root root 5243928576 Jun 8 10:26 sparse
5.2 fake GBs...
Mvh
Mats Johannesson
--
next prev parent reply other threads:[~2006-06-08 8:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 7:34 [PATCH] readahead: initial method - expected read size - fix fastcall Fengguang Wu
2006-06-04 7:34 ` Fengguang Wu
2006-06-04 9:07 ` Andrew Morton
2006-06-04 9:25 ` Arjan van de Ven
2006-06-05 1:17 ` Voluspa
2006-06-05 8:00 ` Arjan van de Ven
2006-06-06 2:26 ` Fengguang Wu
2006-06-06 2:26 ` Fengguang Wu
2006-06-08 7:31 ` Voluspa
2006-06-08 7:57 ` Fengguang Wu
2006-06-08 7:57 ` Fengguang Wu
2006-06-06 2:57 ` Fengguang Wu
2006-06-06 2:57 ` Fengguang Wu
2006-06-08 7:43 ` Voluspa
2006-06-08 8:13 ` Fengguang Wu
2006-06-08 8:13 ` Fengguang Wu
2006-06-08 8:28 ` Voluspa [this message]
2006-06-08 8:50 ` Fengguang Wu
2006-06-08 8:50 ` Fengguang Wu
2006-06-08 10:04 ` Voluspa
2006-06-04 12:13 ` [PATCH] readahead: call scheme - fix fastcall readahead_cache_hit() Fengguang Wu
2006-06-04 12:13 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 3:36 Adaptive Readahead V14 - statistics question Voluspa
2006-05-30 6:40 ` Wu Fengguang
2006-05-30 6:40 ` Wu Fengguang
2006-05-30 16:49 ` Valdis.Kletnieks
2006-05-31 21:06 ` Diego Calleja
2006-05-31 21:50 ` Voluspa
2006-06-01 5:51 ` Fengguang Wu
2006-06-01 5:51 ` Fengguang Wu
2006-06-01 6:35 ` Voluspa
2006-06-08 8:04 ` Voluspa
2006-06-08 11:37 ` adaptive readahead overheads Fengguang Wu
2006-06-08 11:37 ` Fengguang Wu
2006-06-08 12:25 ` Voluspa
2006-06-08 12:39 ` Fengguang Wu
2006-06-08 12:39 ` Fengguang Wu
2006-06-08 13:05 ` Andi Kleen
2006-06-08 14:00 ` Jens Axboe
[not found] ` <448493E9.9030203@samwel.tk>
2006-06-06 3:34 ` Adaptive Readahead V14 - statistics question Wu Fengguang
2006-06-06 3:34 ` Wu Fengguang
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=20060608102802.6e07b148.lista1@comhem.se \
--to=lista1@comhem.se \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wfg@mail.ustc.edu.cn \
/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.