Re: IDE/ATAPI in 2.5

[Christoph Hellwig]

On Tue, Jul 16, 2002 at 04:06:55PM +0200, Joerg Schilling wrote:
> Just a hint: the block layer is for caching blocks from disk type deveices.
> 
> -	Block device access is always going directly into the block cache.
> 	So the I/O is always kernel I/O. In addition, it is async I/O - the 
> 	block layer fires it up and may wait for it later after sending out other
> 	requests.
> 
> -	Character device access is synchronous access and may be either kernel
> 	or user space DMA access. In most cases, it is user space DMA access.
> 
> How try to ask your question again...

The discussion would be much easier if you got the terminology right.
The linux block layer does no caching at all, the caching of the block device
nodes is handles by the page (>= 2.4.10) or buffer (<= 2.4.9) cache.

> >That is not true. Late IDE also has this, and systems like drbd - which
> >currently uses a quite clever heuristic to deduce barriers - could also
> >utilize this input.
> 
> How is it implemented?

RTFS: drivers/ide/tcq.c (in 2.5)