Re: [ovs-dev] [RFC PATCH v2 12/13] Commit push_eth/pop_eth flow action to data plane

2016-07-20 Thread Yang, Yi Y
k the performance is top one for SFC use case. -Original Message- From: Jan Scheurich [mailto:jan.scheur...@ericsson.com] Sent: Wednesday, July 20, 2016 11:07 PM To: Yang, Yi Y ; Li, Johnson ; dev@openvswitch.org Cc: Simon Horman Subject: RE: [ovs-dev] [RFC PATCH v2 12/13] Commit push_eth/po

Re: [ovs-dev] [RFC PATCH v2 00/13] Add Network Service Header Support

2016-07-19 Thread Yang, Yi Y
Jan, although NSH isn't tunnel, but we still need to do some matches after pop_nsh, this is similar to vxlan tunnel, we still can match vxlan tunnel metadata after the patch is de-capsulated, such as TUN_ID and TUN_DST. So my point is maybe we need both header fields and metadata fields. -O

Re: [ovs-dev] [RFC PATCH v2 12/13] Commit push_eth/pop_eth flow action to data plane

2016-07-19 Thread Yang, Yi Y
Hi, Jan How do you know we trigger recirculate after pop_eth? pop_nsh also needs to do so, is there any existing example for reference? -Original Message- From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Jan Scheurich Sent: Tuesday, July 19, 2016 3:46 PM To: Li, Johnson ; dev@

Re: [ovs-dev] [PATCH v9 net-next 4/7] openvswitch: add layer 3 flow/port support

2016-05-09 Thread Yang, Yi Y
I think it is still necessary to keep eth_type in push_eth action, for the classifier case, it will push_nsh then push_eth for the original frame, this will need to set eth_type to 0x894f by push_eth, otherwise push_eth won't know this eth_type. -Original Message- From: dev [mailto:dev-