Date: Tue, 02 Apr 1996 22:46:07 +0100 From: "Gary Palmer" <gpalmer@FreeBSD.ORG> To: Bill Fenner <fenner@parc.xerox.com> Cc: Garrett Wollman <wollman@lcs.mit.edu>, FreeBSD-Current@FreeBSD.ORG Subject: Re: Linker sets & structures for networking code Message-ID: <1252.828481567@palmer.demon.co.uk> In-Reply-To: Your message of "Tue, 02 Apr 1996 09:53:17 PST." <96Apr2.095327pst.177475@crevenia.parc.xerox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Fenner wrote in message ID <96Apr2.095327pst.177475@crevenia.parc.xerox.com>: [ I wrote : ] > >>I can't see how raw_input ever gets call via the localsw > >>array. (Infact there are several examples of `raw_input' being called > >>which bypasses localsw totally). So why on earth is it there?!? > Good question. It probably doesn't belong there either. > (Have you grep'd for pr_input?) gary@palmer:~/cvswork/2.2/sys> grep pr_input */*.[ch] netinet/ip_input.c: (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); netinet/ip_mroute.c: old_proto4_input = inetsw[ip_protox[ENCAP_PROTO]].pr_input; netinet/ip_mroute.c: inetsw[ip_protox[ENCAP_PROTO]].pr_input = X_ipip_input; netinet/ip_mroute.c: inetsw[ip_protox[ENCAP_PROTO]].pr_input = old_proto4_input; sys/protosw.h: * the pr_input and pr_output hooks. Pr_input passes data up (towards sys/protosw.h: void (*pr_input) __P((struct mbuf *, int len)); Huh. Looks like it's just used in the TCP/IP stuff for passing to the appropriate protocol handler. I think it's safe to assume then that the `raw_input' could be replaced with a `0' with no damage. Garrett? Any objections? Or should the entire `raw_*' section be ripped out of localsw? Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1252.828481567>