2016-06-01 15:00, Jasvinder Singh: > This commit adds following features to the routing pipeline; > > 1. Implements the tracking mechanism for the routing pipeline for identifying > the physical nic port where a specific output ports of the routing pipeline > are > eventually connected. Depending upon the application, tracking could involve > traversing the other intermediate pipelines. > > The pipelines such as pass-through allows tracking to be performaned through > them becasue of straightforward connections between their input and output > ports, while pipelines like flow-classifications, firewall fails the tracking > because of dependency upon the table rule set. As a result of tracking > mechainsm, routing pipeline uses the real MAC addresses of the network > interfaces instead of hardcoded default value. > > 2. Adds support for automatic route automatic update when physical NIC ports > change their state (up/down) or configuration. Every time a physical port > goes up/down, a call-back function that the specific pipeline type > (e.g. routing) registered with NIC ports at init time; will simply add/delete > a route associated with that output port. > > Acked-by: Cristian Dumitrescu <cristian.dumitrescu at intel.com> > > Jasvinder Singh (6): > ip_pipeline: increase macros values > ip_pipeline: linking routing pipeline output ports with NIC ports > ip_pipeline: assign nic ports mac address to the routing pipeline > outports > ip_pipeline: automatic routes update with the change in nic ports > state > ip_pipeline: sample config file on adding various network layer > components > ip_pipeline: update release notes
Applied, thanks