Re: [PATCH] scsi/sata write barrier support

[Jeff Garzik]

Jens Axboe wrote:
> On Thu, Jan 27 2005, Jeff Garzik wrote:
>
> > Doug Maxey wrote:
> >
> > > On Thu, 27 Jan 2005 13:02:48 +0100, Jens Axboe wrote:
> > >
> > >
> > > > Hi,
> > > >
> > > > For the longest time, only the old PATA drivers supported barrier writes
> > > > with journalled file systems. This patch adds support for the same type
> > > > of cache flushing barriers that PATA uses for SCSI, to be utilized with
> > > > libata. 
> > >
> > >
> > > What, if any mechanism supports changing the underlying write cache?  
> > >
> > > That is, assuming this is common across PATA and SCSI drives, and it is 
> > > possible to turn the cache off on the IDE drives, would switching the 
> > > cache underneath require completing the inflight IO?
> >
> > [ignoring your question, but it made me think...]
> >
> >
> > I am thinking the barrier support should know if the write cache is 
> > disabled (some datacenters do this), and avoid flushing if so?
>
>
> Ehm it does, read the code :)


I did.  I see nowhere that handles the case where the user uses a util 
(hdparm or blktool) to switch off write cache after sd.c has probed the 
disk.  sd only sets its WCE bit at probe time, and doesn't appear to 
notice state changes.

Since nobody snoops the MODE SELECT on the caching page, nobody knows 
past probe the state of write caching.

Thus my comment...   I think barrier support should know about that sort 
of thing :)

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/