> > > FWIW such an approach is discussed in > > > http://jurassic.sfbay/~nordmark/ip-datapath-design.odt > > > which proposes using a "pre" ip_input functio which does these > > uncomming > > > checks and then calls the "normal" ip_input. That way we can avoid > > > duplicate code. > > > > I see. So where does this leave us? Should I proceed with the > > ill_dhcp_init approach, with the assumption that the datapath refactoring > > project will optimize this codepath to address any performance issues if > > necessary? Or is that not a safe assumption? > > Yes, that sounds like a reasonable plan.
Cool. -- meem
