| To: | Jens Axboe <axboe@xxxxxxx> |
|---|---|
| Subject: | Re: More on write caching |
| From: | Andrew Morton <andrewm@xxxxxxxxxx> |
| Date: | Sat, 07 Jul 2001 21:22:13 +1000 |
| Cc: | Steve Lord <lord@xxxxxxx>, Andrew Klaassen <ak@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| References: | <ak@dkp.com> <20010706130636.C2814@dkp.com> <200107061738.f66Hcpb09219@jen.americas.sgi.com> <3B469DDF.905AEC0B@uow.edu.au>, <3B469DDF.905AEC0B@uow.edu.au> <20010707131328.F16505@suse.de> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
Jens Axboe wrote: > > On Sat, Jul 07 2001, Andrew Morton wrote: > > For more sophisticated storage systems such as RAID controllers, > > I guess we'd have to propagate a SCSI write barrier command down to > > the controller itself. I'm not sure that the Linux request > > and SCSI layers are up to doing that. Have you looked into it? > > I have, I wrote a barrier write patch some time ago. SCSI support is the > easy part, having the luxury of just setting a tag option. Good. Please keep that patch warm. 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? |
| <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, Jens Axboe |
| Previous by Thread: | Re: More on write caching, Jens Axboe |
| Next by Thread: | Re: More on write caching, Jens Axboe |
| Indexes: | [Date] [Thread] [Top] [All Lists] |