Linux-kernel mailing list archive 1999-51,: Re: IDE Driver (Raw Interface) Questions

# Re: IDE Driver (Raw Interface) Questions

Alan Cox (alan@lxorguk.ukuu.org.uk)
Tue, 21 Dec 1999 21:59:24 +0000 (GMT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alan Cox: "Re: Trident audio driver in recent 2.3s"
- Previous message: Matt Robinson: "Re: IDE Driver (Raw Interface) Questions"
- Next in thread: Matt Robinson: "Re: IDE Driver (Raw Interface) Questions"
- Reply: Matt Robinson: "Re: IDE Driver (Raw Interface) Questions"

> |>Post 2.4 there are lots of related things to sort out - passing kiovecs to
> |>block devices, 32bit bounce buffers, and the like. If you had a queue-kiovec
> |>ability then your raw device would be trivial.
>
> Agreed, doing this in post-2.4 will be much simpler, but it doesn't
> make sense to not do it now "just because" ...

I have no problem with you doing it now. Just don't expect the quick hack
approach to make a mainstream kernel.

So wouldn't it be more productive to get the kiovec to block device interface
working. You also btw do need to go via the ll_rw_block request queue at all
times. There is locking in that, there is request merging in that and there
is overlap handling in that.

If you queue a request when the driver knows the queue status or the plug
status you will change behaviours, and I doubt the ide layer will like it

Alan

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

- Next message: Alan Cox: "Re: Trident audio driver in recent 2.3s"
- Previous message: Matt Robinson: "Re: IDE Driver (Raw Interface) Questions"
- Next in thread: Matt Robinson: "Re: IDE Driver (Raw Interface) Questions"
- Reply: Matt Robinson: "Re: IDE Driver (Raw Interface) Questions"