That does help Andrew. What did you mean by having "more than one queue?"
When Netapp support helped us set things up initially, we did segregate data and log files for full recovery databases ( those where transaction log backups can actually be taken ). For simple recovery ( full backups only ) databases, data and log files were located on the same LUN. Tempdb had it's own LUNs as did system databases. Most of these are mirrored to DR.
For the database in question ( aspstate which stores session state info ), there is a very high level of log IO. There is a fair amount of blocking in this database and during busy times, the customers start calling. Actually other solutions that don't keep this information in the database are being explored, but in the interim I thought it would be a virtually free, quick exercise to move this simple recovery database's log file to another LUN.
Local IT management doesn't think it will help since they view the Netapp as one big, albeit smart, bag of disks. What goes on internally in a Netappp storage device is mostly a black box to me.