From: Jan Kara <jack@suse.cz>
To: Wallak <wallak@free.fr>
Cc: Jan Kara <jack@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: File copy is very slow on linux-3.4.2 (or linux-3.3x) on a specific hardware: AMD FX-8150 + 990FX
Date: Tue, 12 Jun 2012 23:09:47 +0200 [thread overview]
Message-ID: <20120612210947.GB20007@quack.suse.cz> (raw)
In-Reply-To: <4FD78CE4.4000209@free.fr>
On Tue 12-06-12 20:39:32, Wallak wrote:
> Jan Kara wrote:
> >On Mon 11-06-12 21:54:16, wallak@free.fr wrote:
> >>I've a very annoying issue on recent kernel (linux-3.4.2-SMP) with my main motherboard (AMD FX-8150 + 990FX - 8 cores 4.1GHz), file copy is very slow (see below). The same kernel works flawlessly on an AMD E450 2 cores motherboard.
> >>
> >>Linux-3.2.20 works properly on this hardware.
> >>hdparm -t gives good results on both kernels.
> >>
> >>I've no idea where this bug come from. Do you have this issue on your hardware ? A patch is available ?
> >>
> >>
> >>*linux-3.4.2
> >>dd if=../in/file_8gb.tmp of=tmp.tmp bs=1024k count=100
> >>100+0 records in
> >>100+0 records out
> >>104857600 bytes (105 MB) copied, 132.884 s, 789 kB/s
> >>
> >>
> >>*linux-3.2.20
> >>dd if=../in/file_8gb.tmp of=tmp.tmp bs=1024k count=100
> >>100+0 records in
> >>100+0 records out
> >>104857600 bytes (105 MB) copied, 3.30793 s, 31.7 MB/s
> > So let's separate reading and writing part first. What is the speed of
> >dd if=../in/file_8gb.tmp of=/dev/null bs=1M count=100
> > on both kernels?
> >And what is the speed of:
> >dd if=/dev/zero of=tmp.tm bs=1M count=100
>
> You're right, the issue is only while writing. The results are below:
>
> #linux-3.4.2
> dd if=/dev/zero of=tmp.tm bs=1M count=100
> 100+0 records in
> 100+0 records out
> 104857600 bytes (105 MB) copied, 151.347 s, 693 kB/s
> dd if=../in/file_8gb.tmp of=/dev/null bs=1M count=100
> 100+0 records in
> 100+0 records out
> 104857600 bytes (105 MB) copied, 1.26228 s, 83.1 MB/s
>
> #linux-3.2.20
> dd if=/dev/zero of=tmp.tm bs=1M count=100
> 100+0 records in
> 100+0 records out
> 104857600 bytes (105 MB) copied, 1.00838 s, 104 MB/s
> dd if=../in/file_8gb.tmp of=/dev/null bs=1M count=100
> 100+0 records in
> 100+0 records out
> 104857600 bytes (105 MB) copied, 1.26947 s, 82.6 MB/s
>
>
> >
> > Also what filesystems are you using?
>
> This is an ext2 file system:
>
> /dev/sda6 ext2 464463364 323380956 141082408 70% /backup
OK, I'm surprised by one thing - how come the writes do no end up cached
in memory (thus you should get much higher throughput). Is the filesystem
mounted with -o sync option by any chance?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2012-06-12 21:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1108815600.134531433.1339443818361.JavaMail.root@zimbra44-e7.priv.proxad.net>
2012-06-11 19:54 ` wallak
2012-06-11 20:48 ` Borislav Petkov
2012-06-11 23:19 ` Wallak
2012-06-12 16:53 ` Jan Kara
2012-06-12 18:39 ` Wallak
2012-06-12 21:09 ` Jan Kara [this message]
2012-06-12 22:41 ` Wallak
2012-06-13 6:53 ` Jan Kara
2012-06-13 20:37 ` File copy is very slow on linux-3.4.2 (or linux-3.3x) on a specific hardware: AMD FX-8150 + 990FX (solved?) Wallak
2012-06-13 22:38 ` Johannes Weiner
2012-06-14 20:16 ` Wallak
2012-06-14 20:57 ` Rik van Riel
2012-06-16 19:32 ` Wallak
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=20120612210947.GB20007@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=wallak@free.fr \
/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
all inboxes | Powered by JetHome®