On Sun, 16 Mar 2008 11:13:42 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:No it doesn't. DRQ simply means "drive has more data for the controller if you want it". Interrupts are controlled via IEN and the interrupt line. If the drive wants to give us data and we end the transaction that is fine. In practice a tiny few devices crap themselves if we don't. A few controllers require specific magic, either to ensure we never touch data after an error, or that we drain enough bits to empty the internal fifo the controller is using to improve ata performance and latches the IRQ arrival against. The PIIX/ICH is as it happens one of the most forgiving controllers anyway. The later ICH (the ones that are also AHCI) are a bit fussier about handling them to the spec because they seem to be some kind of magic ICH emulation layer on an AHCI chip. Alan --
| Zhang, Yanmin | AIM7 40% regression with 2.6.26-rc1 |
| Con Kolivas | [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2 |
| Nick Piggin | [patch 4/6] mm: merge populate and nopage into fault (fixes nonlinear) |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
