Reddy; Anders Widell; Anders Björnerstedt
Cc: opensaf-devel@lists.sourceforge.net
Subject: Re: [devel] [PATCH 0 of 3] Review Request for mds: use TIPC multicast
for MDS broadcast [#851]
On 8/13/2014 3:30 PM, Hans Feldt wrote:
> Why is the finalizesync message so big?
>
> I think that is a c
t; To: mahesh.va...@oracle.com; Hans Feldt; Anders Widell; Anders
>> Björnerstedt
>> Cc: opensaf-devel@lists.sourceforge.net
>> Subject: Re: [devel] [PATCH 0 of 3] Review Request for mds: use TIPC
>> multicast for MDS broadcast [#851]
>>
>> Hi Mahesh,
>
t; To: mahesh.va...@oracle.com; Hans Feldt; Anders Widell; Anders Björnerstedt
>> Cc: opensaf-devel@lists.sourceforge.net
>> Subject: Re: [devel] [PATCH 0 of 3] Review Request for mds: use TIPC
>> multicast for MDS broadcast [#851]
>>
>> Hi Mahesh,
>>
>>>
; Anders Widell; Anders Björnerstedt
>> Cc: opensaf-devel@lists.sourceforge.net
>> Subject: Re: [devel] [PATCH 0 of 3] Review Request for mds: use TIPC
>> multicast for MDS broadcast [#851]
>>
>> Hi Mahesh,
>>
>>>> - A single multicast message can ac
> -Original Message-
> From: Neelakanta Reddy [mailto:reddy.neelaka...@oracle.com]
> Sent: den 13 augusti 2014 11:34
> To: mahesh.va...@oracle.com; Hans Feldt; Anders Widell; Anders Björnerstedt
> Cc: opensaf-devel@lists.sourceforge.net
> Subject: Re: [devel] [PATCH 0 of 3] Review Re
Hi Mahesh,
>>- A single multicast message can accommodate max of MDS_DIRECT_BUF_MAXSIZE
>> (2^16).
The above limit can be removed, because IMM can send the event with grater than
(2^16) size.
After running multiple regression test and do a failover the following is
observed:
The testca
Summary: mds: use TIPC multicast for MDS broadcast [#851]
Review request for Trac Ticket(s): #851
Peer Reviewer(s): Hans/Anders.widell/Anders.bj
Pull request to: <>
Affected branch(es): default
Development branch: default
Impacted area Impact y/n
---