All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.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
Subject: Re: [PATCH v2] sctp: Implement quick failover draft from tsvwg
Date: Wed, 18 Jul 2012 20:30:58 +0000	[thread overview]
Message-ID: <1342643458.2013.32.camel@joe2Laptop> (raw)
In-Reply-To: <1342634466-17930-1-git-send-email-nhorman@tuxdriver.com>

On Wed, 2012-07-18 at 14:01 -0400, Neil Horman wrote:
> I've seen several attempts recently made to do quick failover of sctp transports
> by reducing various retransmit timers and counters.  While its possible to
> implement a faster failover on multihomed sctp associations, its not
> particularly robust, in that it can lead to unneeded retransmits, as well as
> false connection failures due to intermittent latency on a network.

trivia:

> diff --git a/net/sctp/associola.c b/net/sctp/associola.c

> @@ -871,6 +885,10 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
>  		spc_state = SCTP_ADDR_UNREACHABLE;
>  		break;
>  
> +	case SCTP_TRANSPORT_PF:
> +		transport->state = SCTP_PF;
> +		ulp_notify = false;
> +		break;

nicer to add a newline here

>  	default:
>  		return;
>  	}
> @@ -878,12 +896,15 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
[]
> +	if (ulp_notify) {
> +		memset(&addr, 0, sizeof(struct sockaddr_storage));
> +		memcpy(&addr, &transport->ipaddr,
> +		       transport->af_specific->sockaddr_len);

Perhaps it's better to do the memcpy then the memset of the
space left instead.

		memcpy(&addr, &transport->ipaddr, transport->af_specific->sockaddr_len);
		memset((char *)&addr) + transport->af_specific->sockaddr_len, 0,
		       sizeof(struct sockaddr_storage) - transport->af_specific->sockaddr_len);
		       



WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.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
Subject: Re: [PATCH v2] sctp: Implement quick failover draft from tsvwg
Date: Wed, 18 Jul 2012 13:30:58 -0700	[thread overview]
Message-ID: <1342643458.2013.32.camel@joe2Laptop> (raw)
In-Reply-To: <1342634466-17930-1-git-send-email-nhorman@tuxdriver.com>

On Wed, 2012-07-18 at 14:01 -0400, Neil Horman wrote:
> I've seen several attempts recently made to do quick failover of sctp transports
> by reducing various retransmit timers and counters.  While its possible to
> implement a faster failover on multihomed sctp associations, its not
> particularly robust, in that it can lead to unneeded retransmits, as well as
> false connection failures due to intermittent latency on a network.

trivia:

> diff --git a/net/sctp/associola.c b/net/sctp/associola.c

> @@ -871,6 +885,10 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
>  		spc_state = SCTP_ADDR_UNREACHABLE;
>  		break;
>  
> +	case SCTP_TRANSPORT_PF:
> +		transport->state = SCTP_PF;
> +		ulp_notify = false;
> +		break;

nicer to add a newline here

>  	default:
>  		return;
>  	}
> @@ -878,12 +896,15 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
[]
> +	if (ulp_notify) {
> +		memset(&addr, 0, sizeof(struct sockaddr_storage));
> +		memcpy(&addr, &transport->ipaddr,
> +		       transport->af_specific->sockaddr_len);

Perhaps it's better to do the memcpy then the memset of the
space left instead.

		memcpy(&addr, &transport->ipaddr, transport->af_specific->sockaddr_len);
		memset((char *)&addr) + transport->af_specific->sockaddr_len, 0,
		       sizeof(struct sockaddr_storage) - transport->af_specific->sockaddr_len);
		       

  reply	other threads:[~2012-07-18 20:30 UTC|newest]

Thread overview: 48+ 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-13 18:26 ` Neil Horman
2012-07-14 18:12 ` Vlad Yasevich
2012-07-14 18:12   ` Vlad Yasevich
2012-07-14 21:22   ` Neil Horman
2012-07-14 21:22     ` Neil Horman
2012-07-18 18:01 ` [PATCH v2] " Neil Horman
2012-07-18 18:01   ` Neil Horman
2012-07-18 20:30   ` Joe Perches [this message]
2012-07-18 20:30     ` Joe Perches
2012-07-19 10:45     ` Neil Horman
2012-07-19 10:45       ` Neil Horman
2012-07-19 16:54       ` Joe Perches
2012-07-19 16:54         ` Joe Perches
2012-07-18 21:23   ` Vlad Yasevich
2012-07-18 21:23     ` Vlad Yasevich
2012-07-19 10:46     ` Neil Horman
2012-07-19 10:46       ` Neil Horman
2012-07-19 16:51 ` [PATCH v3] " Neil Horman
2012-07-19 16:51   ` Neil Horman
2012-07-20 16:51   ` Flavio Leitner
2012-07-20 16:51     ` Flavio Leitner
2012-07-20 17:19 ` [PATCH v4] " Neil Horman
2012-07-20 17:19   ` Neil Horman
2012-07-20 17:55   ` Vlad Yasevich
2012-07-20 17:55     ` Vlad Yasevich
2012-07-20 18:36     ` Neil Horman
2012-07-20 18:36       ` Neil Horman
2012-07-20 18:51 ` [PATCH v5] " Neil Horman
2012-07-20 18:51   ` Neil Horman
2012-07-20 19:10   ` Flavio Leitner
2012-07-20 19:10     ` Flavio Leitner
2012-07-20 19:31     ` David Miller
2012-07-20 19:31       ` David Miller
2012-07-23 14:28       ` Flavio Leitner
2012-07-23 14:28         ` Flavio Leitner
2012-07-21  6:45   ` Vlad Yasevich
2012-07-21  6:45     ` Vlad Yasevich
2012-07-21 11:03     ` Neil Horman
2012-07-21 11:03       ` Neil Horman
2012-07-21 17:56 ` [PATCH v6] " Neil Horman
2012-07-21 17:56   ` Neil Horman
2012-07-22 18:18   ` Vlad Yasevich
2012-07-22 18:18     ` Vlad Yasevich
2012-07-22 19:14     ` David Miller
2012-07-22 19:14       ` David Miller
2012-07-22 19:18       ` Neil Horman <nhorman@tuxdriver.com>
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=1342643458.2013.32.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --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 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.