On Thu, 2005-12-01 at 11:58 -0500, James.Smart@xxxxxxxxxx wrote: > > > if value is 1 : > > > Interrupts are left enabled, expecting that the user has tuned the > > > interrupt coalescing values. When this setting is enabled, the > > > driver > > > will attempt to service completed i/o whenever new i/o is > > submitted > > > to the adapter. If the coalescing values are large, and the i/o > > > generation rate steady, an interrupt will be avoided by servicing > > > completed i/o prior to the coalescing thresholds kicking in. > > > However, > > > if the i/o completion load is high enough or i/o generation slow, > > > the > > > coalescion values will ensure that completed i/o is serviced in a > > > timely > > > fashion. > > > > this sounds nice.. couldn't this be the default? (even if the delays > > aren't set by default).. > > The real issue with changing the default is that the interrupt coalescing > values affect things that generate interrupts other than just FCP i/o, like > discovery. Tune too high and you might start seeing erroneous ELS errors, > affecting target presentation, recovery after link events, etc. sure.. but if the defaults are 0... why couldn't mode 1 by the default.. isn't mode 1 with coalesing value 0 the same as mode 0.. and if so.. why need a mode 0 in the first place ? - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
