Sebastien Roy wrote:
Sebastien Roy wrote:
There's already this kind of relationship between ip_rput() and
ip_input(), with ip_input() meant to be the "fast" input routine
which makes assumptions about being called from either GLDv3 or
ip_rput() itself. One could loosen ip_input()'s restrictions
regarding alignment,
s/loosen/tighten/ :-)
etc., by modifying ip_rput() and the input paths in dls without
adding any new input paths in the ip module.
I had a similar thought after looking at the code. (Although one
potential difference is what happens on putbq... I've not given that any
consideration as of yet.)
Is IP itself careful never to internally generate or modify a message
that winds up leaving it in an "unaligned" (or non-contiguous IP header)
state? E.g. what about IP tunnels? I've not looked at this carefully
yet, but I'd love to have the input of an expert in the code.
- Garrett
_______________________________________________
networking-discuss mailing list
[email protected]
