To summarise the discussion on the pfhooks work... (From Eric, Kacheong and Xiaobo) The topic of being able to be notified about changes in hooks present for an event was raised. Given the diverse interest in this, I'll look at how this can be designed in. - action
(From Jim) To make the current events more useful, the per-event data structures need to carry some information about which zone they occurring in. - action (add net_data_t to both event data structures) (From Jim) Being able to convert between the instance identifier (netid_t) bring introduced here and zoneid_t is required. - action (add new interfaces to map zoneid_t and netid_t) (From Eric Wang) Being able to reinject packets into the network stack is a feature that is best left for the IP refactoring project, where we plan to carry around packet attributes, internal to IP. - postpone (this requires revisiting IP's data paths) (From Jim) Document how the functions in netinfo map onto existing networking ioctls. - action (expand documentation) (From Jim) Only allow one hook to specify and use the _FIRST/_LAST hints at any one time for a given event. -action (modify code to return EEXIST for late comer) (From Jim) Make the ordering hints _BEFORE and _AFTER allow for their dependents to not be present as well as being present. - investigate (add a flag, HF_HINT_LOOSE to h_flags to allow dependencies from these to not exist when the hook is added.) ..Have I mised anything? Darren _______________________________________________ networking-discuss mailing list [email protected]
