From: Mark H. <ma...@os...> - 2004-03-30 17:37:18
|
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. -- Mark Haverkamp <ma...@os...> |