Thread: [Fwd: Re: [Tipc-discussion] tipc-1.3.08 and tipc_test-1.4 at SF]

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi,
The API changes are not binary compatible. (And not source code
compatible either, for that sake.) I think we can take that penalty now,
since the old version only is used by Ericsson people, and they are
maintaining
their own line for some time, at least. The ethereal module also needs
to be
updated, but I would wait with that, the IETF discussions and "reliable
multicast" implementation may still lead to further (small) changes in
the 
protocol header.

I think most urgent now is to port the test suite developed by Nicolas
Gendron
et al (it is at SF) over to the new API, and ensure that it works all
the
way. SOCK_STREAM and link changeover has not been tested, either. The
first
one is new, and the second one is partially rewritten, because I wanted
to simplify
 it. (We only support two active links per node pair now, instead of 4.)

Also, Kconfig is just a sketch now, and needs to be updated, smething
similar
to what you had in yours and Mika's version, but maintaining
possiblility to
standalone build. This requires default values when Kconfig is not used,
as far as I can understand. E.g. something like this (net.h):
#ifndef MAX_ZONES
#define MAX_ZONES 15
#endif

If you feel you have time for any of this, I would be very grateful.

Regards /Jon

Mark Haverkamp wrote:

On Mon, 2004-03-29 at 20:31, Jon Maloy wrote:

Hi all,

I just checked in a new version of the "unstable" TIPC, and added a
matching

file release. It is a lot more stable than the previous version, but it 

is not

ready to move over to the "stable" CVS package yet.

By mistake I put the file release under the "tipc_source" line, but when

considering it, I  don't think that is so bad to start using that one 

now, so

I will  let it stay there.

I also added a file release version of "tipc_test", the benchmark
program

I have been using as basic test program. It runs all the way to the end
at

my SMP machines, with a 2.6.4 kernel. It is infested with debug
printouts,

but should otherwise be useful for your testing.

Note that I have changed the directory structure and makefiles, to be

able to support both linux 2.4 and 2.6, as long as that is needed.

I realized that the SF directory structure under any circumstances

will be different from what TIPC will look like in the Linux kernel,

if/when that happens, so it does not really matter what we

put up there. It should just be as maintainable as possible for
ourselves.

I will be in Europe the next two weeks, and will not be able to do much

programming over there. But I will read and answer emails.

Regards /Jon

I have the new driver running on my 2.6.5-rc2 SMP machines.  I initially

had problems using applications though.  Even though the tipc drivers

could see each other I couldn't communicate between applications.  I did

some looking around and found the the format of sockaddr_tipc changed. 

There is a scope element.  This breaks any already compiled code running

on the previous versions of tipc.

Also, has anyone updated the ethereal tipc module to work with the new

protocol version?

Mark.

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.

Thread: [Fwd: Re: [Tipc-discussion] tipc-1.3.08 and tipc_test-1.4 at SF]

Cluster wide IPC providing datagram, connection, and bus messaging

tipc-discussion