I'm not sure that enough detail is provided for
this to be "automatic" and there is also the problem
of the missing UDP probes... see below.
On 03/31/10 10:36, Adam Leventhal wrote:
B. DESCRIPTION
This work will introduce the following probes for the 'tcp' provider:
tcp:::send
tcp:::receive
tcp:::connect-request
tcp:::connect-refused
tcp:::connect-established
tcp:::accept-established
tcp:::accept-refused
tcp:::state-change
If we do simple trackng of accept-established and
connect-established, we're able to count how many
active connections there are but to properly adjust
the counter when things close requires tracking
state-change and understanding enough of TCP
to know how to adjust your stats correctly.
Futher to this, if I look at tcp:::connect-request
and tcp:::state-change, is that enough or do I also
need the other tcp:::connect's to detect when a
connection request is refused? The state of the
TCP socket should go from SYN-SENT to
CLOSED for connect-refused. Similarly,
connect-established should just be a alias for
the transition of SYN-SENT to ESTABLISHED
and accept-established a change from
SYN-RECEIVED to ESTABLISHED.
Is that all correct? Will a dtrace script that
gathers connect-established and state-change
have both of those probes activated for the
same event?
Given this, it would be appreciated if some text
mentioned whether the above are actually aliases
or not.
With all of those state-change aliases available
on the connect side, I'm curious about why the
close side has been ignored.
Is there a reason why we don't have "tcp:::closed"?
Furthermore, whilst the case is titled "DTrace
TCP and UDP providers", I only see TCP ones
presented but an example with UDP. The materials
need to be updated to specify which UDP ones are
being introduced.
Darren
_______________________________________________
opensolaris-arc mailing list
[email protected]
