Audsin wrote: > I am currently working in the fragmentation avoidance technique caused by > the overhead introduced by MIP6. I am using FreeBSD 4.4 and Kame Snap. > I have introduced some code in netinet6/ip6_output.c code and > netinet6/in6_pcb.h and netinet/in_pcb.h so that length of the MIP6 > extension header if present is taken into account, when calculation the > ipoptlen() and hence frag is avoided. Below i am pasting the code to which > i have made changes. The lines starting with @ symbol shows the code > introduced by me. Please go thru the code and let me know whether this > takes account of the Extension header length introduced by MIP6. Since, > this is my first research project, i kindly request you to go thru the code > and help me. > I have explained my code under the heading "Implementation" in the last ie. > after the codes > > Please let me know, whether this code will take into account the length > occupied by MIP6 Ext header. If any changes is required pls let me know. > > Thanks and sorry for the disturbance
We saw it the first two times you sent it. The patch, as is, is unreadable. It would be much more useful to the list if you were to use "cvs diff" to obtain the diff. If you are not using a checked out source tree from a local copy of the CVS repository to do your developement, then "diff -c" is is good, too (unidiffs are less useful because your version is not likely to match our version, since FreeBSD 4.4 predates some significant stack changes, such as SYN caching, etc.). The most correct place to send this request is the "[EMAIL PROTECTED]" list, not the "[EMAIL PROTECTED]" list. All that in mind, it looks like the code oes what you want, which appears to be avoiding fragmentation in the multicast datagram; however, with the diff being as unreadable as it is, no one is likely to step through the full output code path while holding your diff in their head. As a general observation, I'd like to know (1) Is this what it's supposed to do?, (2) If you are talking about multicast datagrams, how is it that you are getting fragmentation without going over the MTU in the first place, is packet coelescing that's biting you?, (3) What's the performance difference you expect out of doing this? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
