Bug #837

cpu localize dummynet(4) stage 1

Added by sepherosa almost 7 years ago. Updated over 6 years ago.

Status:ClosedStart date:
Priority:LowDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi all,

Following patch is the first step to cpu-localize dummynet(4); this
patch also completely decouples dummynet(4) and ipfw(4):
http://leaf.dragonflybsd.org/~sephe/dummynet_cpu0.diff

Please review it.

I want to put various dummynet(4) related bits in netinet/ip_input.c
into net/dummynet/ip_dummynet_glue.c, which will be marked as
"standard" in conf/files. Any suggestions?

Best Regards,
sephe

History

#1 Updated by sepherosa almost 7 years ago

New patch is generated:
http://leaf.dragonflybsd.org/~sephe/dummynet_cpu1.diff

Following things are changed in the new patch:
- a bug was fixed (it exists in the original dummynet code): rtentry
may be not UP when we redispatch packets back to its origins.
- nuke module and header file dependency of ipfw in dummynet code
- moved all of the dummynet related changes in netinet/ip_input.c into
net/dummynet/ip_dummynet_glue.c

Please review/test it. If no objection comes, it will be committed on Thursday.

Best Regards,
sephe

Also available in: Atom PDF