From: Flavio Leitner <fbl@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: netdev@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>,
Sridhar Samudrala <sri@us.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
linux-sctp@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH v3] sctp: Implement quick failover draft from tsvwg
Date: Fri, 20 Jul 2012 13:51:39 -0300 [thread overview]
Message-ID: <20120720135139.34f2c8c9@obelix.rh> (raw)
In-Reply-To: <1342716704-6532-1-git-send-email-nhorman@tuxdriver.com>
On Thu, 19 Jul 2012 12:51:44 -0400
Neil Horman <nhorman@tuxdriver.com> wrote:
[...]
>
> +pf_retrans - INTEGER
> + The number of retransmissions that will be attempted on a given path
> + before traffic is redirected to an alternate transport (should one
> + exist). Note this is distinct from path_max_retrans, as a path that
> + passes the pf_retrans threshold can still be used. Its only
> + deprioritized when a transmission path is selected by the stack. This
> + setting is primarily used to enable fast failover mechanisms without
> + having to reduce path_max_retrans to a very low value. See:
> + http://www.ietf.org/id/draft-nishida-tsvwg-sctp-failover-05.txt
> + for details. Note also that a value of pf_retrans > path_max_retrans
> + disables this feature
> +
> + Default: 0
> +
> rto_initial - INTEGER
[...]
> diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
> index e4652fe..f70726c 100644
> --- a/include/net/sctp/structs.h
> +++ b/include/net/sctp/structs.h
> @@ -160,6 +160,7 @@ extern struct sctp_globals {
> int max_retrans_association;
> int max_retrans_path;
> int max_retrans_init;
> + int pf_retrans;
[...]
>
> + /* This is the partially failed retrans value for the transport
> + * and will be initialized from the assocs value. This can be changed
> + * using the SCTP_PEER_ADDR_THLDS socket option
> + */
> + int pf_retrans;
> /* PMTU : The current known path MTU. */
> __u32 pathmtu;
>
> @@ -1660,6 +1667,8 @@ struct sctp_association {
> */
> int max_retrans;
>
> + int pf_retrans;
> +
You've documented in one place, but not in the others. I suggest to include
references like this
/* See the description in struct sctp_transport */
at the two missing places.
Nice feature,
fbl
next prev parent reply other threads:[~2012-07-20 16:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 18:26 [PATCH] sctp: Implement quick failover draft from tsvwg Neil Horman
2012-07-14 18:12 ` Vlad Yasevich
2012-07-14 21:22 ` Neil Horman
2012-07-18 18:01 ` [PATCH v2] " Neil Horman
2012-07-18 20:30 ` Joe Perches
2012-07-19 10:45 ` Neil Horman
2012-07-19 16:54 ` Joe Perches
2012-07-18 21:23 ` Vlad Yasevich
2012-07-19 10:46 ` Neil Horman
2012-07-19 16:51 ` [PATCH v3] " Neil Horman
2012-07-20 16:51 ` Flavio Leitner [this message]
2012-07-20 17:19 ` [PATCH v4] " Neil Horman
2012-07-20 17:55 ` Vlad Yasevich
2012-07-20 18:36 ` Neil Horman
2012-07-20 18:51 ` [PATCH v5] " Neil Horman
2012-07-20 19:10 ` Flavio Leitner
2012-07-20 19:31 ` David Miller
2012-07-23 14:28 ` Flavio Leitner
2012-07-21 6:45 ` Vlad Yasevich
2012-07-21 11:03 ` Neil Horman
2012-07-21 17:56 ` [PATCH v6] " Neil Horman
2012-07-22 18:18 ` Vlad Yasevich
2012-07-22 19:14 ` David Miller
2012-07-22 19:18 ` Neil Horman <nhorman@tuxdriver.com>
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=20120720135139.34f2c8c9@obelix.rh \
--to=fbl@redhat.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=sri@us.ibm.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).