Those of you using afe (and also mxfe) will be pleased to note that the time is fast approaching when afe will hopefully be integrated into Solaris Nevada. There is a PSARC fasttrack scheduled for it next week if I understand correctly. (I don't have the case number yet.)
There are a few ramifications of this. One of the most immediate is that I'm going to be winding down support for versions of Solaris earlier than 10. In fact, I no longer have any personal installations running anything less than S10u3, and most everything is running Nevada.
The other reason for me to do this is so that I can immediately start taking advantage of some features that are present in Solaris 10 and Nevada. For example, I want to add support for DLPI link notification, and ultimately (in Nevada) port to GLDv3.
The GLDv3 has some compelling features, and as a result afe and mxfe will gain support for features like vlans, jumbo frames, and interrupt blanking. And, they'll also benefit from the increased performance gains afforded by the GLDv3 framework.
It isn't clear to me that I'll be supporting GLDv3 for Solaris 10 (the interfaces are not yet public), but at least in Nevada I will. And even for S10, I'll probably be using new GLDv2 features that are not available to older releases. (Like the DLPI link notification.)
Before I do this, I will be spinning one last significant bug fix release for afe and mxfe, which addresses several significant bugs found by Sun's QA group. (Including the fact that afe has not functioned properly with multicast since it was first written!)
Watch the web page for more details.