From: Vlad Y. <vla...@hp...> - 2007-03-26 17:39:01
|
Son Le wrote: > Thanks Vald. The patch was done at the kernel level which is like a > black box to us. So I assume that if we use the latest lksctp_too.1.0.6 > which has the new sctp.h and new implemenation (at user space level ?) > of sctp_getpaddr and sctp_getladdr in addr.c. I am not sure whats the > linkage between the APIS in the addr.c and the kernel. > You need to make sure that the socket option number used in the kernel matches that from the library. > I have another big question as well. > > Does application needs the implementations (e.g. sctp_gepaddr(), ...) > from the lk_sctptool OR just use the sctp.h header file provided by the > tools and call to the APIs will be invoked from the actual kernel. This depends on the option numbers used. Generally, all that's need is a call to the API. The library knows the kernel interface and talks to the kernel. -vlad > > Thanks, > Son > > -----Original Message----- > From: Vlad Yasevich [mailto:vla...@hp...] > Sent: Monday, March 26, 2007 10:58 AM > To: Le, Son (CAR:SI52) > Cc: lks...@li... > Subject: Re: Rissue with patching back sctp_getpaddr and sctp_getladdr > from 2.6.19 to 2.6.10 > > Son Le wrote: >> We also compile the below directory too. Not sure if the 2 APIs >> sctp_getladdr and sctp_getpaddr in the addrs.c mismatche with the one >> in the kernel source ? The sctp kernel is maintained by other people >> and we don't know what is in it. >> >> zcarh0xa.ca.nortel.com-149>ls >> Build.mk bindx.c opt_info.c recvmsg.c >> addrs.c connectx.c peeloff.c sendmsg.c >> zcarh0xa.ca.nortel.com-150> >> > > The API change you want affects both use and kernel space. You need to > make sure that the sctp library uses the new kernel interface. > > Of course, you can always call the socket options directly, but that is > not a recommended way to do this. > > -vlad |