From: Thomas Graf <tgraf@suug.ch>
To: Vlad Yasevich <vyasevich@gmail.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
Michele Baldessari <michele@acksyn.org>,
linux-sctp@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] sctp: support per-association stats via a new SCTP_GET_ASSOC_STATS call
Date: Tue, 30 Oct 2012 14:54:44 +0000 [thread overview]
Message-ID: <20121030145444.GO13450@casper.infradead.org> (raw)
In-Reply-To: <508FE256.9010205@gmail.com>
On 10/30/12 at 10:21am, Vlad Yasevich wrote:
> What if the message arrived across multiple transports?
>
> Also, you can always see current rto, but that means that the
> application has to still poll for it with PEER_ADDR_INFO. I think
> the idea, as Thomas pointed out, is to easily see what the max rto
> was. I like that, but I don't like the fact that it's per
> association. With that stat we really don't know which transport
> spiked. So, it gives us a some useful information, but not really
> enough.
>
> It might be a little more useful to keep track of the which
> transport has experienced the spike and then return info about it.
> Granted, we may be too late and the spike corrected itself already,
> but at least it will give the management application a little more
> information and allow admin to have a little more info to determine
> why the spike occurred.
Agreed and good point, a per transport max rto makes more sense.
next prev parent reply other threads:[~2012-10-30 14:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 13:42 [PATCH net-next] sctp: support per-association stats via a new SCTP_GET_ASSOC_STATS call Michele Baldessari
2012-10-26 14:37 ` Neil Horman
2012-10-26 19:16 ` Vlad Yasevich
2012-10-27 11:35 ` Michele Baldessari
2012-10-27 15:48 ` Vlad Yasevich
2012-10-27 15:50 ` Vlad Yasevich
2012-10-29 16:38 ` Neil Horman
2012-10-29 20:11 ` Vlad Yasevich
2012-10-29 22:19 ` Neil Horman
2012-10-29 8:41 ` Thomas Graf
2012-10-29 11:37 ` Neil Horman
2012-10-29 20:22 ` Vlad Yasevich
2012-10-30 11:15 ` Neil Horman
2012-10-30 14:21 ` Vlad Yasevich
2012-10-30 14:54 ` Thomas Graf [this message]
2012-10-30 12:52 ` Thomas Graf
2012-10-30 14:25 ` Vlad Yasevich
2012-10-30 14:51 ` Thomas Graf
2012-10-26 20:00 ` Vlad Yasevich
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=20121030145444.GO13450@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=michele@acksyn.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).