| To: | Andrew Morton <andrewm@xxxxxxxxxx> |
|---|---|
| Subject: | Re: More on write caching |
| From: | Jens Axboe <axboe@xxxxxxx> |
| Date: | Sat, 7 Jul 2001 13:28:39 +0200 |
| Cc: | Steve Lord <lord@xxxxxxx>, Andrew Klaassen <ak@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20010707132238.G16505@xxxxxxx> |
| References: | <ak@xxxxxxx> <20010706130636.C2814@xxxxxxx> <200107061738.f66Hcpb09219@xxxxxxxxxxxxxxxxxxxx> <3B469DDF.905AEC0B@xxxxxxxxxx>, <3B469DDF.905AEC0B@xxxxxxxxxx> <20010707131328.F16505@xxxxxxx> <3B46F0E5.77EAF1F9@xxxxxxxxxx> <20010707132238.G16505@xxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Sat, Jul 07 2001, Jens Axboe wrote: > > Question is: does IDE need it at all? If we can assume > > that the data is safe once the drive has acked it, then that's > > all a journalling fs cares about, yes? Plus, BTW, this is what breaks too I'm afraid: 'If we can assume that the data is safe once the drive has acked it' is too easy to "optimize" by manufacturers. One can only hope and pray that they at least honor a sync cache flush, but hey... -- Jens Axboe |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: More on write caching, Jens Axboe |
|---|---|
| Next by Date: | Re: More on write caching, Andrew Morton |
| Previous by Thread: | Re: More on write caching, Jens Axboe |
| Next by Thread: | Re: More on write caching, Andrew Morton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |