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]

Message-ID: <201104011334.24182.charles@cariden.com>
Date:	Fri, 1 Apr 2011 13:34:24 -0700
From:	Charles Samuels <charles@...iden.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Queuing of disk writes

On Friday, April 01, 2011 1:10:49 pm Alan Cox wrote:
> > 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.
Generally 64KiB - I don't know disk geometry, but I guess that's a lot smaller 
than a cylinder.

But I don't really care about throughput (much), I care more about my 
application not blocking everything while the fsync happens.

> 
> > 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.

I've seen this on ext3, ext4, and XFS. Reiser3 not so much. I've also 
convinced my users to use write-backed cache. They're Enterprise customers and 
have loads of money to spend on hardware, such as Warp Cores.

> 
> The ultima answer is probably an SSD of course 8)
Well, that would solve the throughput, but it doesn't solve the blocking!

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