linux-kernel - Re: Very poor latency when using hard drive (raid1)

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] [day] [month] [year] [list]

Message-ID: <20130419150156.GC26647@quack.suse.cz>
Date:	Fri, 19 Apr 2013 17:01:56 +0200
From:	Jan Kara <jack@...e.cz>
To:	"lkml@...usoft.pl" <lkml@...usoft.pl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Very poor latency when using hard drive (raid1)

On Mon 15-04-13 11:59:59, lkml@...usoft.pl wrote:
> There are 2 hard drives (normal, magnetic) in software raid 1
> on 3.2.41 kernel.
  Any possibility in trying a newer kernel? Like 3.8 / 3.9?

> When I write into them e.g. using dd from /dev/zero to a local file
> (ext4 on default settings), running 2 dd at once (writing two files) it
> starves all other programs that try to use the disk.
  That shouldn't really happen. I presume you use the default IO scheduler?
i.e. CFQ?

> Running ls on any directory on same disk (same fs btw), takes over half
> minute to execute, same for any other disk touching action.
> 
> Did anyone seen such problem, where too look, what to test?
  Not in such a simple setting as yours.

> What could solve it (other then ionice on applications that I expect to
> use hard drive)?
  ionice wouldn't help because dd writes the data into page cache and from
there flusher thread writes them to disk. So IO happens in flusher context
which won't be ioniced.

									Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/