From: "James Carlson" <[EMAIL PROTECTED]>
Darren Reed writes:
Really, the action here is upon the Solaris networking community to:
1) make db_credp or equivalent functionality part of the DDI;
2) make crfree or equivalent functionality part of the DDI;
3) investigate what other things should be in the DDI that are related.
Or, perhaps better yet:
B) Make sure that non-DDI cruft like this doesn't leak where it's
not needed. If we made certain that only cr-aware drivers (and
perhaps modules as well) would see this, I think we'd be in a
better place.
I think what you're missing here is that someone wants to use
the db_credp because it holds useful information for whatever
it is they're doing.
Removing it because it is non-DDI cruft, without providing another
means to access that information, would seem like a step backwards
to me. Looking at Sun doing that, without providing another means
to access this information, from an external perspective would seem
to me like Sun being hostile towards my desires as a developer.
And to me that is contrary to what OpenSolaris is meant to be about.
Which is why I want to know what the requirements are that led to
the question about this being raised. I can see lots of reasons why
someone would want to use the db_credp on an mblk. I think
we're much better served by understanding the requirements and
then taking some action than simply deciding that this is cruft and
removing it.
So while your (B) seems like a nice thing, I'd venture to say that it
is a non-starter without first understanding what the API gap is
here that someone wants to use it for and having a path to
undertake fixing that.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
