From: Andrea Arcangeli <andrea@suse.de>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Slow Disk I/O with QPS M3 80GB HD
Date: Thu, 13 Dec 2001 00:49:33 +0100 [thread overview]
Message-ID: <20011213004933.T4801@athlon.random> (raw)
In-Reply-To: <20011210203452.A3250@lucon.org> <20011210235708.A17743@lucon.org> <20011211154331.A32433@lucon.org> <20011212092954.N4801@athlon.random> <20011212153806.A22202@lucon.org>
In-Reply-To: <20011212153806.A22202@lucon.org>; from hjl@lucon.org on Wed, Dec 12, 2001 at 03:38:06PM -0800
On Wed, Dec 12, 2001 at 03:38:06PM -0800, H . J . Lu wrote:
> H.J.
> ----
> 3 files on USB:
>
> # ls -l
> total 5984
> -rwxr-xr-x 1 root root 1991481 Dec 8 21:44 dsc00002.jpg
> -rwxr-xr-x 1 root root 2432127 Dec 8 23:54 dsc00005.jpg
> -rwxr-xr-x 1 root root 1675563 Dec 8 23:59 dsc00009.jpg
>
> 1. 2.4.10-pre10
>
> # time /bin/cp * /tmp/
> real 0m0.623s
> user 0m0.000s
> sys 0m0.100s
>
> 2. 2.4.10-pre10aa1
>
> # time /bin/cp * /tmp/
> real 0m8.952s
> user 0m0.000s
> sys 0m0.190s
>
>
> 3. 2.4.10-pre11
>
> # time /bin/cp * /tmp/
> real 0m8.851s
> user 0m0.000s
> sys 0m0.170s
but the above have nothing to do with the blkdev-pagecache.
Blkdev-pagecache can matter only with blkdev accesses, blkdev-pagecache
cannot make any difference if the I/O passes through any fs (not via the
block_dev layer) like in the above case.
Can you try to take those cp under strace timestamp and see what's the
syscall that blocks?
Andrea
next prev parent reply other threads:[~2001-12-12 23:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011210203452.A3250@lucon.org>
2001-12-11 7:57 ` Slow Disk I/O with QPS M3 80GB HD H . J . Lu
2001-12-11 16:05 ` Ben Collins
2001-12-11 16:45 ` H . J . Lu
2001-12-11 17:05 ` Ben Collins
2001-12-11 17:20 ` H . J . Lu
2001-12-11 23:43 ` H . J . Lu
2001-12-12 8:29 ` Andrea Arcangeli
2001-12-12 23:38 ` H . J . Lu
2001-12-12 23:49 ` Andrea Arcangeli [this message]
2001-12-13 0:11 ` H . J . Lu
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=20011213004933.T4801@athlon.random \
--to=andrea@suse.de \
--cc=hjl@lucon.org \
--cc=linux-kernel@vger.kernel.org \
/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