>> In any case, that's moot since I now understand why mac_open() can't >> be used to enable or disable the fast-path. > > Hmmm... maybe IP needs a variant of mac_open(), or some other way to > differentiate it. > > My biggest concern is still that have certain clients that have to > explicitly disable fast path, but only for legacy NICs. I'm not quite > ready to throw in the towel on this one. > > Is there not some way that we could do something special for IP (the > main fast path consumer, I believe) apart from other mac clients? > > Maybe its not worth worrying about, seeing as this API is private > anyway. But I *really* *REALLY* hope that it will just plain go away > before the MAC API is published. I have little real hope of that > though, so I'd prefer to see effort expended now to make at least the > public API boundaries fast-path (and clearview!) agnostic. > I understand your concern, but I cannot see the solution to these. A variant mac_open() won't work because mac_open() (or its variant) is called by DLPI applications (not only IP) when they open the /dev/net nodes, before we cannot even determine whether it is IP or not.
Thanks - Cathy
