Re: [PATCH 5/7] libata: move and reduce locking to the pio data xfer functions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Yeah, it's not a water-tight solution.  I don't think we can do that
> with IRQ enabled during transfer.  So, we can have either highly jerky
> but reliable system if PIO is used or usually better behaving PIO with
> some chance of getting nobody-cared.  Also, we can flag known buggy
> devices/controllers such that IRQ is disabled over PIO by default.  I
> think it's worth doing but this definitely should be debated better.

Which leaves us back at enable/disable_irq as with the old IDE - which
*are* much better because most of the time the IRQ isn't shared. Sucks
when it is but that is life.
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux