> > I don't know if there is any way to turn of a write buffer on an IDE disk. > You want a forced set of commands to kill caching at init? Wrong model You want a write barrier. Write buffering (at least for short intervals) in the drive is very sensible. The kernel needs to able to send drivers a write barrier which will not be completed with outstanding commands before the barrier. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Re: scsi vs ide performance on fsync's Douglas Gilbert
- Re: scsi vs ide performance on fsync's Ishikawa
- Re: scsi vs ide performance on fsync's Douglas Gilbert
- Re: scsi vs ide performance on fsync's Douglas Gilbert
- Re: scsi vs ide performance on fsync's Linus Torvalds
- Re: scsi vs ide performance on fsync's Jonathan Morton
- Re: scsi vs ide performance on fsync's dean gaudet
- Re: scsi vs ide performance on fsync's dean gaudet
- Re: scsi vs ide performance on fs... Jonathan Morton
- Re: scsi vs ide performance on fsync's Andre Hedrick
- Re: scsi vs ide performance on fsync's Alan Cox
- Re: scsi vs ide performance on fsync's Linus Torvalds
- Re: scsi vs ide performance on fs... Stephen C. Tweedie
- Re: scsi vs ide performance o... Jens Axboe
- Re: scsi vs ide performance o... Andre Hedrick
- Re: scsi vs ide performance on fsync's Mike Black
- Re: scsi vs ide performance on fsync's Jeremy Hansen
- Re: scsi vs ide performance on fs... Jonathan Morton
- Re: scsi vs ide performance on fs... Jeremy Hansen
- Re: scsi vs ide performance o... Linus Torvalds
- Re: scsi vs ide performance o... Stephen C. Tweedie