From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] cman: Fix udpb handling in cman-preconfig
Date: Tue, 04 Jan 2011 10:05:58 +0100 [thread overview]
Message-ID: <4D22E2F6.90505@redhat.com> (raw)
In-Reply-To: <4D22E191.1040606@redhat.com>
On 1/4/2011 10:00 AM, Jan Friesse wrote:
> Lon,
> even it may "logically" seemed that original code is incorrect and your
> patch make sense, it's not the case.
>
> Actually, corosync has 3 transports:
> udp, udpu and iba.
>
> Broadcast is same transport as udp but only has broadcast flag set on.
>
> In other words, this patch is not correct.
>
So in order to configure broadcast we still need to use:
<cman transport="udp" broadcast="yes"/> ?
I find that redundant tho...
Cheers
Fabio
> Regards,
> Honza
>
> Lon Hohberger wrote:
>> Signed-off-by: Lon Hohberger <lhh@redhat.com>
>> ---
>> cman/daemon/cman-preconfig.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/cman/daemon/cman-preconfig.c b/cman/daemon/cman-preconfig.c
>> index 5239d89..5d608a7 100644
>> --- a/cman/daemon/cman-preconfig.c
>> +++ b/cman/daemon/cman-preconfig.c
>> @@ -286,7 +286,7 @@ static int add_ifaddr(struct objdb_iface_ver0 *objdb, char *mcast, char *ifaddr,
>> int ret = 0;
>> const char *tx_mech_to_str[] = {
>> [TX_MECH_UDP] = "udp",
>> - [TX_MECH_UDPB] = "udp",
>> + [TX_MECH_UDPB] = "udpb",
>> [TX_MECH_UDPU] = "udpu",
>> [TX_MECH_RDMA] = "iba",
>> };
>
next prev parent reply other threads:[~2011-01-04 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 18:19 [Cluster-devel] [PATCH] cman: Fix udpb handling in cman-preconfig Lon Hohberger
2011-01-04 9:00 ` Jan Friesse
2011-01-04 9:05 ` Fabio M. Di Nitto [this message]
2011-01-04 9:18 ` Jan Friesse
2011-01-04 20:06 ` Lon Hohberger
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=4D22E2F6.90505@redhat.com \
--to=fdinitto@redhat.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).