A phone meeting of the TIPC working group was held on March 29, 2007. Attendees: Al Stephens (Wind River) -- meeting chair; Jon Maloy (Ericsson); Randy MacLeod (Nortel); Dominic Herity (Red Plain); Lijun Chen (Nortel); Elmer Horvath (Wind River)
Minutes: 1. Meeting opening. The meeting was called to order at 11:02 AM (EDT). 2. Non-contiguous sk_buff support update. Randy has provided a more complete patch for supporting sk_buffs containing more than one fragment; Al will reivew this & provide additional feedback. Randy also suggested it would be a good idea to look at adding "all round" support for fragmented sk_buffs, in addition to his current receive path work. Giving the send path the ability to create sk_buffs using multiple smaller-sized fragments might result in better memory utilization, and lessen the burden on the operating system to provide large chunks of contiguous memory. Al will add this to the TIPC wish-list. 3. Hierarchical TIPC design update. The design issues identified by Al at the last meeting were discussed the following week by Al, Jon, Maarten Koning, Elmer, and Aldo MacFarlane, and an action plan was created. Al has subsequently implemented some of the changes discussed, including: - increasing the # of Ethernet bearers support by TIPC from 2 to 8, - separating routing table functionality from name table functionality (reusing code where possible to reduce duplication), - introducing a new "route distribution" message type, and - optimizing the purging of unreachable name table entries and severing broken connections when connectivity with a node (or cluster, or zone) is lost. Along the way, Al has created a lot of the infrastructure needed to support the addition of "network scope" service naming, in addition to the existing node, cluster, and zone scopes. The major item not yet addressed is the addition of routable links (aka "linklets"), which are needed to improve the performance and reliability of messages sent between clusters or zones. Al will probably not begin this work for a month or two, as he needs to stabilize the upcoming TIPC 1.7.3 software for release in mid-May. Jon and Al then discussed some ideas involving the separation of logical Link functionality from physical Link (aka "Trunk") functionality. Further discussion will be postponed until Al is ready to begin work in this area. 4. Link stability question. Dominic inquired about currently known issues involving link instability (link flopping). Randy and Jon replied that it shouldn't be an issue if the link tolerance is not set too small, but no one has actually tested this recently to see what the lower limit really is. 5. Performance update. Elmer is coordinating activities in this area. A new participant (Florian) has offered to assist with this work; Hari (from OpenClovis) will also be directed to this area. 6. Bond interface update. Jon reported that he's still waiting on Ericsson management to approve the release of the bond interface code Randy is interested in seeing. 7. redFOX announcement. Dominic reported that he will be sending out an announcement about the addition of TIPC support to the redFOX high performance distributed object infrastructure. 8. Patch submission update. Jon reported he is still working on the small patch Al recently supplied for inclusion into the TIPC 1.6 stream. The main source of the delay is the updating required to Jon's development environment, which had not been used in a long time. 9. Meeting close. The meeting adjourned at 11:50 AM. The next meeting is scheduled for Thursday, April 26th at 11:00 AM EDT. Please let me know of any errors or omissions. Regards, Al Stephens [END] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ tipc-discussion mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
