[Tipc-discussion] New file release tipc-1.3.10

[Jon M. <jon...@er...>]

Hi all,
I just uploaded a new file release to SourceForge.
I have corrected several bug related to message bundling and
link changeover, plus a very serious lock bug that sometimes
caused my processors to hang when they lost contact with each
other.
I also corrected a bug in the name/network subscription code,
so you will now receive an event for all overlapping, already
existing publications, not only the first one found ;-).
Some left-out symbols were finally exported as they should.

There are still problems, and strange behaviour that puzzles me,
but it is getting stabler by the day. Among the problems I see:

---When I run the benchmark program, there seems to be a much wider
    time lapse between the termination of the first process and the last
    one for a certain message size than I would expect. The benchmark
     runs to the end without problems, but this does not look right, and
     influences the benchmark result.

--- Even apart from the above, performance seems to be poorer than
     in the old version (the 1.2-line) , for no obvious reason. With the 
code
     changes I have done, I would expect about the same performence.
     At least on SMP the figures look bad, despite the fine lock 
granularity
     we have now. This must be investigated. I have not done any comparative
     measurements on the same hardware and same kernel with the two TIPC
      versions, so this is just an impression I have, but the figures 
worry me.
     Anybody  feeling a vocation here ?


Also, I plan to announce TIPC at the LKML by the end of this week. We must
admit that the code is still in beta status, but as I understand it this 
should
be no problem.
In relation to this, I would like to have a better overview of the code 
status.
Has anybody tested the management interface all the way (Mark?)
Has anybody tried the SOCK_STREAM interface yet ?
What is the status of the multicast code ? (there were some discussions
about who should receive the messages last week, -has this been followed up
with corrections) ?
The reliable broadcast code ?
Are there any known bugs/problems that have not been corrected yet.

Regards /jon