it is possible to specify the bind network and
the networking will take place over that interface.
(Logical change 1.14)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@30 fd59a12c-fef9-0310-b244-a6a79926bd2f
as root in order to lock, set RR 99, and
bind to a specific ethernet interface for multicast.
(Logical change 1.14)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@29 fd59a12c-fef9-0310-b244-a6a79926bd2f
UDP sockets, bind to specific interface defined in network.conf.
This is done by creating two fds. gmi_fd_token is used for all
token communication. gmi_fd_mcast is used for all mcast
communication. I'm not sure if gmi_fd_mcast binding rules is
correct. Once work begins on multipathing, this will have to
be figured out :)
2004/06/23 13:55:52-07:00 mvista.com!sdake
Use portable mreq instead of mreqn when joining the multicast
group.
(Logical change 1.13)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@26 fd59a12c-fef9-0310-b244-a6a79926bd2f
port being byte swapped. This of course, doesn't work well with
xscale boards.
(Logical change 1.9)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@17 fd59a12c-fef9-0310-b244-a6a79926bd2f
the recursion by queueing single node message delivery as a timer
with 0 timeout. This was happening before, but the logic was
wrong.
(Logical change 1.7)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@13 fd59a12c-fef9-0310-b244-a6a79926bd2f
because the initial send of the token is sent to the wrong address.
2004/06/16 15:42:49-07:00 mvista.com!sdake
Performance enhancements: Allow more messages to be multicast per
token possession to reach 8.8MB/sec checkpoint performance without
remcasts. Trim gather/commit timeouts to 100 msec to speed up the
membership gathering process.
(Logical change 1.5)
git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@10 fd59a12c-fef9-0310-b244-a6a79926bd2f
