[Linux-decnet-user] Starting to get routing into shape
Brought to you by:
chrissie_c,
ph3-der-loewe
|
From: Steven W. <st...@gw...> - 2003-04-08 16:13:12
|
Hi, I've had a little time recently to work on the routing for DECnet. I've got a patch against 2.5.67 which is rather large which fixes a number of issues which have been outstanding for some time. It also brings into the DECnet code some bug fixes which were introduced into the ipv4 routing code after the DECnet routing code was split from it. Some of the fixes need back porting into 2.4 and I may get time to do that over the next few weeks, but its not an easy thing to do since so much has changed. I suspect that very few people are using the routing code in the 2.4 kernel version of DECnet anyway. Since the patch is large I've not attached it, but it can be found here: http://www.chygwyn.com/~steve/kpatch/ I'm also intending to submit it to the 2.5 kernel very shortly. Some of the features are: o Two bugs fixed (only in 2.5 decnet stack) relating to bind and connection states. o Numerous style changes: using C99 initialisers and inline rather than __inline__ o Use struct flowi as routing key (for forthcoming flow cache) o Add metrics to routing table o Many routing table bug fixes o New wait code to improve efficiency o New module interface functions o We use real device MTUs now rather than saying "hmm... looks like ethernet must be 1500" as we used to (still one or two places to fix, but its mostly correct in this patch) o Tidy up in af_decnet.c:dn_sendmsg() in preparation for zerocopy o Updates to rtnetlink code to return more information o Removed ioctl() for decnet fib. It never did anything and rtnetlink is a far better interface anyway. o Converted /proc/decnet_neigh to seq_file (other /proc files to follow) o DECnet route cache now uses RCU like the ipv4 route cache o Misc bug fixes wherever I found them I would recommend all users of DECnet in 2.5 to upgrade to this patch as soon as it makes it into the standard kernel. As always - let me know if you have any comments or questions or spot any more bugs! Steve. |