On May 22, 2014 at 3:35:37 AM, Franck BAUDIN (franck.bau...@qosmos.com) wrote:
> Do you plan to expose the ct->mark (CONNMARK) as an OpenFlow matcher, as it > was done for > the sk_buff->mark (pkt_mark)? My current design doesn't specify that, but I will likely add it. It's a logical addition. > With an application aware conntrack-engine (thanks to ALGs or to a DPI > engine) storing > the "Application ID" in the connmark, we could then use compact matchers > based on CONNMARK. > Let's say RTP correspond to connmark=0x55, and you want to steer all RTP > traffic in a specific > QoS queue: > ovs-ofctl add-flow br0 connmark=0x55,action= set_queue:123 Yes, as we discussed before, that is a possibility. It will need to interact with whatever else is on that system, since there are such a limited number of bits. Whoever is administering that box will need to deal with potentially multiple applications that want to use those bits, so some care will need to be taken about assuming that they are available to you. --Justin _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
