linux-kernel - Re: 2.6.24-rc3-mm1 (sync is slow ?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20071121004909.6157bb9a.akpm@linux-foundation.org>
Date:	Wed, 21 Nov 2007 00:49:09 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.24-rc3-mm1 (sync is slow ?)

On Wed, 21 Nov 2007 17:42:15 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:

> Hi, Andrew
> 
> I got following result in 'sync' command.
> It was too slow. (memory controller config is off ;)
> I attaches my .config.
> ==
> [2.6.24-rc3-mm1]
> [kamezawa@...test2 ~]$ dd if=/dev/zero of=./tmpfile bs=4096 count=100000
> 100000+0 records in
> 100000+0 records out
> 409600000 bytes (410 MB) copied, 1.46706 seconds, 279 MB/s
> [kamezawa@...test2 ~]$ time sync
> 
> real    3m6.440s
> user    0m0.000s
> sys     0m0.133s
> 
> 
> on, 2.6.23-rc2-mm1, 2.6.23-rc3 there was no problem.
> ==
> [2.6.24-rc3]
> [kamezawa@...test2 ~]$ dd if=/dev/zero of=tmpfile bs=4096 count=100000
> 100000+0 records in
> 100000+0 records out
> 409600000 bytes (410 MB) copied, 2.07717 seconds, 197 MB/s
> [kamezawa@...test2 ~]$ time sync
> 
> real    0m9.935s
> user    0m0.001s
> sys     0m0.113s
> 
> [2.6.24-rc3]
> [kamezawa@...test2 ~]$ dd if=/dev/zero of=./tmpfile bs=4096 count=100000
> 100000+0 records in
> 100000+0 records out
> 409600000 bytes (410 MB) copied, 1.37147 seconds, 299 MB/s
> [kamezawa@...test2 ~]$ time sync[2.6.24-rc2-mm1]
> 
> 
> real    0m11.718s
> user    0m0.000s
> sys     0m0.138s

Well I wonder how we did that.

It seems OK here from a quick test (i386, ext3-on-IDE).

Maybe device driver/block breakage?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/