Over the past few months, we (the Intel networking group) have been working hard, often off-list, to get the I/OAT patches we've posted here merged into the mainline kernel branch, as well as Red Hat and SuSE. We've had some success, but not what's really important: getting it into the mainline kernel releases.
Of course some of this can be blamed on how a corporate culture approaches the open source community when it thinks it has something that gives it a competitive advantage in the marketplace. If we acted like jerks, it's just because we think we have something good here! :) But seriously, I know we've had longer turnaround times in releases and replying to comments than people have liked. All we can say is sorry, we really have been doing our best. People were kind enough to review our patches and suggest over 50 improvements, we have fixed the patches accordingly, and we really do appreciate it. So OK assume we have a nice pretty patchset. Why should it go in? Since we have an NDA with Red Hat we've been trying to convince DaveM and Red Hat of I/OAT's merits off-list, but this kind of change needs a more public airing of all its pros and cons. We have posted all the performance data we have gathered so far on the linux-net wiki: http://linux-net.osdl.org/index.php/I/OAT , and listed the overall concerns that have been expressed in private. I'm hoping you will look at the data, re-examine the patches, and then we can talk about the technical issues here on the list, getting down to the specifics, so we can hash it out in public and settle on the right path to take. Thanks -- Regards -- Andy - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
