All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [PATCH 2/3] sctp: export SctpT1Retransmits to /proc/net/sctp/snmp
Date: Tue, 06 Jul 2010 13:38:20 +0000	[thread overview]
Message-ID: <4C3331CC.2040907@hp.com> (raw)
In-Reply-To: <4C2DA094.3000601@cn.fujitsu.com>

Shan Wei wrote:
> Hi vlad:
> 
> Vlad Yasevich wrote, at 07/02/2010 10:31 PM:
>> Why do you need that when we already have SctpT1InitExpireds and
>> SctpT1CookieExpireds.  Just sum them together and you get the
>> the T1_RETRANSMITS.
> 
> T1_RETRANSMITS is not equal to the summation of  SctpT1InitExpireds
> and SctpT1CookieExpireds.
> 
> If an host received stale cookie error at COOKIE-ECHOED state,
> it will sent a new INIT chunk to the endpoint and restart to set up
> the association. The resented new INIT chunk is counted to T1_RETRANSMITS.
> 
> SctpT1InitExpireds/SctpT1CookieExpireds is counted for timeout event of
> T1_INIT/T1_COOKIE.
> 

So I fail to see the usefulness of showing and even keeping that counter.
When you look at the value, what new information will it provide you?

If it is only the retransmissions due to stale cookie error, then by all
means, track that value instead.  That would actually provide new and useful
data.  That's really the gist of my objection.  There is no reason to track
and display useless pieces of information.

-vlad

      parent reply	other threads:[~2010-07-06 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02  8:17 [PATCH 2/3] sctp: export SctpT1Retransmits to /proc/net/sctp/snmp Shan Wei
2010-07-02 14:31 ` Vlad Yasevich
2010-07-05  2:14 ` Shan Wei
2010-07-06 13:38 ` Vlad Yasevich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C3331CC.2040907@hp.com \
    --to=vladislav.yasevich@hp.com \
    --cc=linux-sctp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.