Quoting r. Roland Dreier <[EMAIL PROTECTED]>: > Anyway I don't think this is that urgent -- we've dumped enough stuff > into 2.6.19, so I think this should wait for 2.6.20 at the earliest anyway.
Hmm, iwarp went in, ehca went in, OK. Pathscale are dumping out their internal tree at a high rate. But if you look at IPoIB over mthca for example, there were almost no changes. Isn't that true? And isn't the NAPI patch quite small? Maybe, if you are worried about stability, we can make NAPI optional and off by default in 2.6.19? There's precedent for this with e1000. This would also give low level driver maintainers the chance to experiment and select the best API's, instead of just guessing which one is best. In 2.6.20 we'll be able to remove the non-NAPI path if it works out well. Want to see a patch like this? -- MST _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
