Re: Kernel Summit request for Discussion of future of ATA (libata) and IDE

[Alan Cox <alan@lxorguk.ukuu.org.uk>]

>   - "difficult" legacy PC-class hardware (i.e. secondary interface on
> CY82C693 etc)

Yep - probably an hours work but I've simply not been able to get the
relevant hardware to test.

> * There are still regressions in many libata PCI host drivers dating back
>   to their rushed introduction.

I don't think we have any that are real straight forward "you
forgot something" regressions now. There are a few "works with A not B"
cases in both directions that we'll probably take ages to figure out.

> * There are still corner case in libata core - PIO is dead slow
> compared to drivers/ide/,

There are two there - libata keeps IRQs blocked for longer in PIO mode as
well which is a factor for realtime that needs looking at, as well as
using 16bit not 32bit I/O for most devices (which is trivial to fix). The
IRQ masking stuff is more complex and old IDE handles it far better for
PIO on non shared IRQ interfaces. That is actually probably the most
complicated thing to address of the stuff you'd want to do if you were
going to kill off old IDE.

>   "serialized" hosts are not supported, some quirks for obsolete
> hardware got lost...

Serialized hardware has been supported since 2.6.24 or so. Not sure there
are any quirks for obsolete hardware now missing but its always fun
trying to nail them all. Libata can support per command serializing and
pretty much arbitarily complex serializing rules via qc_defer.

> > The proposal is to discuss the future of these two subsystems and arrive
> > at a consensus what's happening to each going forwards.
> 
> Well, I'm looking forward to discuss the future of Linux ATA support.

Have fun, but don't expect me to respect any decisions made off public
lists. I don't really see any point worrying about it - porting m68k to
libata is of minimal value for example and there is little likelyhood of
Amiga AHCI SATA suddenely appearing.

Alan