netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Maloy <jon.maloy@ericsson.com>
To: Holger Brunck <holger.brunck@keymile.com>,
	"davem@davemloft.net" <davem@davemloft.net>
Cc: Ying Xue <ying.xue@windriver.com>,
	Erik Hugne <erik.hugne@ericsson.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH net-next] tipc: allow one link per bearer to neighboring nodes
Date: Wed, 6 May 2015 19:45:18 +0000	[thread overview]
Message-ID: <A2BAEFC30C8FD34388F02C9B3121859D1C3F0AC1@eusaamb103.ericsson.se> (raw)
In-Reply-To: <1415986399-23874-1-git-send-email-holger.brunck@keymile.com>

Hi Holger,
I am trying to remember why you wanted to have this, especially since it
didn't change anything in practice, because MAX_BEARERS is still 2.

This limit has to be changed, since we may want to have e.g. dual Ethernet
links to some nodes and single UDP links to others (but never the same)

Despite this, I can find good reasons to not allow more than two links 
between a node pair. (In particular, the failover mechanism becomes 
much more complex)

Can you please reiterate why you see a need for this?

Regards
///jon


> -----Original Message-----
> From: Holger Brunck [mailto:holger.brunck@keymile.com]
> Sent: Friday, November 14, 2014 12:33 PM
> To: davem@davemloft.net
> Cc: Jon Maloy; Holger Brunck; Ying Xue; Erik Hugne; netdev@vger.kernel.org
> Subject: [PATCH net-next] tipc: allow one link per bearer to neighboring
> nodes
> 
> There is no reason to limit the amount of possible links to a neighboring node
> to 2. If we have more then two bearers we can also establish more links.
> 
> Signed-off-by: Holger Brunck <holger.brunck@keymile.com>
> Reviewed-By: Jon Maloy <jon.maloy@ericsson.com>
> cc: Ying Xue <ying.xue@windriver.com>
> cc: Erik Hugne <erik.hugne@ericsson.com>
> cc: netdev@vger.kernel.org
> ---
>  net/tipc/link.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/net/tipc/link.c b/net/tipc/link.c index 1db162a..7cf8004 100644
> --- a/net/tipc/link.c
> +++ b/net/tipc/link.c
> @@ -224,9 +224,10 @@ struct tipc_link *tipc_link_create(struct tipc_node
> *n_ptr,
>  	char addr_string[16];
>  	u32 peer = n_ptr->addr;
> 
> -	if (n_ptr->link_cnt >= 2) {
> +	if (n_ptr->link_cnt >= MAX_BEARERS) {
>  		tipc_addr_string_fill(addr_string, n_ptr->addr);
> -		pr_err("Attempt to establish third link to %s\n", addr_string);
> +		pr_err("Attempt to establish %uth link to %s. Max %u
> allowed.\n",
> +			n_ptr->link_cnt, addr_string, MAX_BEARERS);
>  		return NULL;
>  	}
> 
> --
> 2.1.2

  parent reply	other threads:[~2015-05-06 20:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 17:33 [PATCH net-next] tipc: allow one link per bearer to neighboring nodes Holger Brunck
2014-11-16 19:27 ` David Miller
2015-05-06 19:45 ` Jon Maloy [this message]
2015-05-11  8:26   ` Holger Brunck
2015-05-11 16:10     ` Jon Maloy

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=A2BAEFC30C8FD34388F02C9B3121859D1C3F0AC1@eusaamb103.ericsson.se \
    --to=jon.maloy@ericsson.com \
    --cc=davem@davemloft.net \
    --cc=erik.hugne@ericsson.com \
    --cc=holger.brunck@keymile.com \
    --cc=netdev@vger.kernel.org \
    --cc=ying.xue@windriver.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).