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]
Date:	Sun, 16 Jul 2006 09:38:25 -0700
From:	"Jonathan Baccash" <jbaccash@...il.com>
To:	"Avi Kivity" <avi@...o.co.il>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: raid io requests not parallel?

> Each head has to service 1024 write requests (compared to just 512 read
> requests).

By that logic, it would take twice as long for my writes to finish.
Why is it taking 4x as long in my parallel test? I don't think any of
the repliers understood my question. What I want to know is, during a
single direct IO write request, I would expect the raid software to
issue the write request to both disks simultaneously. But the evidence
indicates that isn't what is happening. I would expect a raid-1 write
to take about as long to write a single block as a single write to a
single disk (assuming no other disk activity), because I would expect
two writes to happen concurrently.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ