It occurs to me that, as this has the potential to break Virtual Synchrony, there should be an option to either disable message fragmentation or to some indication of the maximum message size that will not be fragmented. Thoughts? Chrissie On 12/02/15 16:39, Christine Caulfield wrote: > As we discussed at the cluster summit, increasing the message size > inside corosync itself is not only dangerous, but is only needed for a > very few corner cases .. all of which involve CPG. > > So, to allow large CPG messages (which is needed) I have added an extra > facility to libcpg that will fragment messages that are too large for > corosync's internal buffers. It does this transparently to the > application. zero-copy sends are NOT supported for this feature. > > I've also included a test program 'cpghum' that can test this facility > with message sequence numbers and checksums. > > Signed-Off-By: Christine Caulfield <ccaulfie@xxxxxxxxxx> > > > > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
