[PATCH] sata_nv: Don't attempt using ADMA for (READ|SET)_MAX commands

2007-04-13 Thread Kyle McMartin
READ_NATIVE_MAX and SET_MAX were causing timeouts on sata_nv controllers. Disabling ADMA helped, but that is quite a large hammer to use. Reverting 382a6652e91b34d5480cfc0ed840c196650493d4 also helped, but we might as well fix it right, instead of disabling the performance gain on cache flushes by

Re: [PATCH] sata_nv: Don't attempt using ADMA for (READ|SET)_MAX commands

2007-04-13 Thread Alan Cox
On Fri, 13 Apr 2007 13:08:31 -0400 Kyle McMartin [EMAIL PROTECTED] wrote: READ_NATIVE_MAX and SET_MAX were causing timeouts on sata_nv controllers. Disabling ADMA helped, but that is quite a large hammer to use. Reverting 382a6652e91b34d5480cfc0ed840c196650493d4 also helped, but we might as

Re: [PATCH] sata_nv: Don't attempt using ADMA for (READ|SET)_MAX commands

2007-04-13 Thread Mark Lord
Alan Cox wrote: On Fri, 13 Apr 2007 13:08:31 -0400 Kyle McMartin [EMAIL PROTECTED] wrote: READ_NATIVE_MAX and SET_MAX were causing timeouts on sata_nv controllers. Disabling ADMA helped, but that is quite a large hammer to use. Reverting 382a6652e91b34d5480cfc0ed840c196650493d4 also helped,

Re: [PATCH] sata_nv: Don't attempt using ADMA for (READ|SET)_MAX commands

2007-04-13 Thread Robert Hancock
Mark Lord wrote: Alan Cox wrote: On Fri, 13 Apr 2007 13:08:31 -0400 Kyle McMartin [EMAIL PROTECTED] wrote: READ_NATIVE_MAX and SET_MAX were causing timeouts on sata_nv controllers. Disabling ADMA helped, but that is quite a large hammer to use. Reverting