Same here. Trained to reply and not reply-all.
Begin forwarded message:
From: Erik O'Shaughnessy <erik.oshaughne...@sun.com>
Date: 16 April, 2009 4:43:26 PM CDT
To: Jason King <ja...@ansipunx.net>
Subject: Re: [perf-discuss] kstat stability tags
On 16 Apr, at 4:21 PM, Jason King wrote:
On Thu, Apr 16, 2009 at 4:07 PM, Peter Tribble <peter.trib...@gmail.com
> wrote:
On Tue, Apr 7, 2009 at 8:25 PM, Jason King <ja...@ansipunx.net>
wrote:
To get around the hurdle of all kstats being effectively private,
which in turn makes it difficult to effectively build any sort of
tools that use them,
That hasn't stopped plenty of tools being developed, though.
Yes, but based on the discussion here, even though there's lots of
stuff already in ON that use kstats directly, even though there are
unbundled products that use kstats sold by Sun, adding another one
will apparently not be allowed without getting something like this
pushed through unless it's done by someone with a Sun badge.
I think there is a fundamental misunderstanding here. I have a Sun
badge and my proposal (PSARC 2008/502 rpc.kstatd) was stopped dead
in the water due kstat data (in)stability. Please don't think you
are being singled out because you are not a Sun employee. Don't
take it too personally would be my advice. I think what you are
trying to do right now is positive and I hope that it continues that
way.
AFAIK, the current kstat interfaces are effectively frozen.
The user-land kstat interfaces are currently classified as 'stable'
which means that changes to them will be restricted to major point
releases ( I think, that's from memory ). The point being, they can
be changed over time with enough patience.
Another possible design would be to do away with the separate call,
and simply appropriate the (currently unused)ks_resv field in the
kstat
structure to hold the stability data.
Good idea :)
---
erik.oshaughne...@sun.com:Strategic Applications Engineering, Austin
Texas:512-401-1070
---
erik.oshaughne...@sun.com:Strategic Applications Engineering, Austin
Texas:512-401-1070
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
