Sorry for my written mistake, that's dst ip addr. The email context updated as
follows:
In my test, add one flow to br-ovs, and running one vm connected this br-ovs:
cookie=0x0, duration=286.272s, table=31, n_packets=2, n_bytes=196,
idle_age=161, priority=61010,ip,metadata=0x2b193,dl_dst=00:00:00:04:06:03
actions=move:NXM_OF_IP_DST[]->NXM_NX_REG0[],load:0x8439ce602f->OXM_OF_METADATA[],resubmit(,32)
when sending packets with random dst ip addr from vm, I found many datapath
exact flows are gernerated instead of one megaflow entry. One dst ip generated
one exact flow.
What's the megaflow match policy about move:NXM_OF_IP_DST? Why we don't using
megaflow wildcard on the openflow actions of move:NXM_OF_IP_DST[]?
Thank you!
B.R.
Lilijun
-----邮件原件-----
发件人: Lilijun (Jerry, Cloud Networking)
发送时间: 2018年4月4日 11:56
收件人: d...@openvswitch.org; 'Ben Pfaff' <b...@ovn.org>
抄送: lixiao (H) <lixia...@huawei.com>; gaoxiaoqiu <gaoxiao...@huawei.com>
主题: Question about ovs megaflow with move NXM_OF_IP_DST actions
Hi all,
In my test, add one flow to br-ovs, and running one vm connected this br-ovs:
cookie=0x0, duration=286.272s, table=31, n_packets=2, n_bytes=196,
idle_age=161, priority=61010,ip,metadata=0x2b193,dl_dst=00:00:00:04:06:03
actions=move:NXM_OF_IP_DST[]->NXM_NX_REG0[],load:0x8439ce602f->OXM_OF_METADATA[],resubmit(,32)
when sending packets with random source ip addr from vm, I found many datapath
exact flows are gernerated instead of one megaflow entry. One source ip
generate on exact flow.
What's the megaflow match policy about move:NXM_OF_IP_DST? Why we don't using
megaflow wildcard on the openflow actions of move:NXM_OF_IP_DST[]?
Thank you!
B.R.
Lilijun
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
