A phone meeting of the TIPC working group was held on December 20, 2007.

Attendees:

Al Stephens (Wind River) -- meeting chair; Elmer Horvath (Wind River);
Randy Macleod (Nortel); Ravi Rao (Nortel associate); Jon Maloy
(Ericsson) 

Minutes:

1. Meeting opening

The meeting was called to order at 11:09 AM (EST).

2. TIPC on Solaris update

Laurent Ganne and Renaud Metrich (Sun) were unable to attend, but sent
emails to Al describing their activities over the last 3 weeks.  Laurent
has make rapid progress and is now able to use tipc-config to trigger a
request/reply exchange with the TIPC kernel code on OpenSolaris, however
the reply isn't valid; he also has additional coding and testing to do
in the socket and Ethernet media areas.  Renaud is investigating kernel
mods needed to add AF_TIPC socket support to Solaris 10.  This topic
will be reviewed again in a month; Al will post both emails to the TIPC
mailing list for greater visibility.

3. Recent TIPC contributions

A number of new contributions to TIPC have been released over the last 3
weeks, including:
- a project that allows TIPC to be invoked from Python
- a patch that allows TIPC 1.7.5 to run on Linux 2.6.23 kernels
- an updated version of the portable TIPC test suite (PTTS), for both
Linux and VxWorks
- a patch that allows TIPC 1.5.12 to support multiple TIPC stacks on a
single node
  (this is discussed more under item 5)

Al has updated the TIPC website to make these contributions more
accessible to users.

There has also been a semaphore-related patch made to TIPC 1.6 by the
Linux kernel team.  Al will investigate shortly to ensure that there are
no unexpected issues associated with it.

4. TIPC 1.7 integration into Linux kernel

The preceding contributions highlight the importance of integrating the
TIPC 1.7 code base into the Linux kernel, since the limited resources of
the working group do not allow us the luxury of maintaining two
different code streams and the integration effort only increases the
longer we wait.  Al has finally got a resourcing commitment from his
management team, and will begin the integration at the start of February
once his current non-TIPC project work is done.  The completion date for
the integration effort is uncertain, since this is the first large set
of patches submitted for TIPC since TIPC 1.6 was first integrated.

Al outlined a 3 stage approach for the integration: 1) integration of
bug fixes and minor enhancements (under the TIPC 1.6 banner), 2)
integration of the new file naming structure (under the TIPC 1.8
banner), and 3) integration of the new TIPC features (such as
hierarchical TIPC).  This approach will allow the changes that are of
greatest benefit to most users (and least likely to be controversial) to
be integrated first.  The working group members gave there support to
this proposal.

5. TIPC virtualization update

Randy requested feedback on the vTIPC patch he recently posted, as
he/Ravi want to integrate it into the Nortel proprietary code stream for
TIPC in early January.  Al agreed to do a quick review before the
holiday shutdown period begins (Friday afternoon); if needed, he will do
a more comprehesive review when he returns on January 2nd.

Randy also received the go-ahead to post the vTIPC patch to the Linux
kernel team for approval in principle.  This will provide an opportunity
to gather early feedback about any major issues that would prevent the
patch from being accepted by the Linux kernel folks once the TIPC 1.7
integration work has been done.

6. tipcdump question

Randy asked if tipcdump had been integrated into the standard TIPC code
stream; Al replied that it was not.

7. Meeting close

The meeting adjourned at 11:45. The next meeting is scheduled for
Thursday, January 31 at 11:00 AM EST.

Please let me know of any errors or omissions.

Regards,
Al Stephens

[END]


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Reply via email to