On 4/28/05, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote: > On Mer, 2005-04-27 at 19:40, mike.miller@xxxxxx wrote: > > It looks like the OS/filesystem (ext2/3 and reiserfs) does not wait for for a successful completion. Is this assumption correct? > > Of course it doesn't. At 250 ops/second for a decent disk no OS waits > for completions, all batch and asynchronously queue I/O. See man fsync > and also O_DIRECT if you need specific "to disk" support. If you do that > be aware that you must also turn write caching off on the IDE disk. I've > repeatedly asked the "maintainer" of the IDE layer to do this > automatically but gave up bothering long ago. Without that setting users WTF is wrong with you Alan? We agreed on this but it is you to do coding, if you want it, not me (and there was never any patch from you). It is not my (unpaid) job to fulfill any requirement you come up with. BTW I was supposed to push git update today but I wasted this time on replying your complaints (didn't even bother with personal insults). > are playing with fire quite honestly. > > The alternative with latest 2.6 stuff is to turn on Jens Axboe's barrier > work which seems to give better performance on a drive new enough to > have cache flush operations. - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
