Re: about link congestion handle

As I stated in my previous response, creating a patch to restore native API support is not just a symbol
matter of adding EXPORT_SYMBOL calls. The removal of native API support means that many of the routines
that were provided are no longer present, and may of those that remain are being simplified because they
can now leverage the fact that they are only invoked by callers using the socket API. Attempting to undo
these changes will be a non-trivial matter that will become progressively harder as changes to the Linux
kernel continue to alter the behavior of the socket-only implementation of TIPC.

-- Al

> -----Original Message-----
> From: lzy.dev <at> gmail.com [mailto:lzy.dev <at> gmail.com] 
> Sent: Wednesday, December 01, 2010 8:47 PM
> To: Stephens, Allan
> Cc: tipc-discussion
> Subject: Re: [tipc-discussion] about link congestion handle
> 
> bottom-posting.
> 
> On Wed, Dec 1, 2010 at 7:00 PM, Stephens, Allan 
> <allan.stephens <at> windriver.com> wrote:
> > lzy wrote:
> >
> >> On Wed, Dec 1, 2010 at 4:54 AM, Jon Maloy <jon.maloy <at> ericsson.com> 
> >> wrote:
> >> > Hi Lzy,
> >> > Maybe Allan also should have warned you that the native
> >> interface is being removed as a public interface. You will not be 
> >> able to use this in the future without patching (exporting 
> symbols) 
> >> the code.
> >> >
> >> > Regards
> >> > ///jon
> >
> >> Hi, all:
> >>
> >>     to Stephens, Allan: thx, I will try to send message 
> again later 
> >> when tipc throw congestion.
> >>
> >>     to Jon Maloy: thx about you note, could you tell me 
> more detail 
> >> about this native api patch? I use tipc 2.0.0 mod in
> >> rhel5.4/centos-5 (kernel 2.6.36.1) os, the native functions like 
> >> tipc_send working still. What time should I do exporting symbols 
> >> patching for native api in  manual? thank you.
> >>
> >> Zhi Yan, Liu
> >
> > TIPC's native API is still available in 2.6.36, but it won't be 
> > available in 2.6.37 or later. If you're planning on using 
> TIPC in the 
> > long term you should consider modifying your application to use the 
> > socket API, since this will be the only supported API.
> >
> > While it will still be theoretically possible for you to patch the 
> > Linux kernel to restore native API support you would have to create 
> > the patch yourself, and this would require an extremely detailed 
> > understanding of TIPC's internal operations -- something that would 
> > take a very long time to acquire. Also, you'd end up using 
> a patched 
> > version of TIPC that isn't supported by the TIPC Working Group. It 
> > would be far less effort and far safer to avoid using such a patch.
> >
> > Regards,
> > Al
> >
> 
> Hi, AI:
> 
>     right that.
> 
>     by the way, If i try to create a patch about restore tipc 
> native api in future version, is it a bit thin? sush as just 
> need me to add
> EXPORT_SYMBOL(tipc_send) code? OR the tipc mod has some 
> structural changes? this is important to development of app in future.
> 
>     thanks!
> 
> Zhi Yan, Liu
> 
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev