linux-kernel - Re: Queuing of disk writes

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:	Fri, 1 Apr 2011 21:10:49 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Charles Samuels <charles@...iden.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Queuing of disk writes

> the kernel's write cache, and then consequently the disk drive's DMA queue. As 
> a result of that, the harddrive can pick the correct order to do these writes, 
> significantly reducing seek times.

Well that depends a lot on the data, if its very scattered and random it
may not help much.

> And yes, I *know* fsync is a poor method to determine if data is actually 
> committed to something non-volatile. :)

fsync/fdatasync should at least make sure it hit the disk. If barriers
are enabled the rest too.

What file system are you using - some of the file systems have serious
limits in this are around fsync and ordering and you may be hitting those.

The ultima answer is probably an SSD of course 8)

Alan
--
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/