Re: [ovs-discuss] OVS megaflows

I took a look at the datapath code - saw only single table, which its entries are microflows and megaflows the megaflows are indicated by non-zero mask fields Sara On Wed, Aug 16, 2017 at 9:59 AM, Sara Gittlin wrote: > Thank you Joe > Few questions: > 1. Are there 2

Re: [ovs-discuss] OVS megaflows

Thank you Joe Few questions: 1. Are there 2 separate flow tables in the kernel data-path ? for microflows and megaflows ? 2. If the answer is yes : - When pkt arrives, is it first checked against the microflows table and if there is no match, then it checked against the megaflows table ?

Re: [ovs-discuss] OVS megaflows

On the first point - it's a little more subtle than that. A traffic flow (eg, a connection) must arrive at OVS, the first packet is sent through userspace, which causes userspace to install a megaflow into the datapath. Subsequently, if any traffic which matches that megaflow arrives, it will

Re: [ovs-discuss] OVS megaflows

Can i summarize: 1. Once N microflows are installed in the kernel cache: we can install a megaflow/s in kernel datapath, if it possible to generate a megaflow/s for them 2. These megaflow/s remain in the kernel megaflow cache as long as the associated flows are in userspace openflow tables,

Re: [ovs-discuss] OVS megaflows

The FAQ is referring to megaflows as well, the reasons are the same. Neither microflows nor megaflows can be pre-populated. On 14 August 2017 at 00:35, Sara Gittlin wrote: > I understand that this citation refers to the kernel microflows tables. > the kernel megaflows

Re: [ovs-discuss] OVS megaflows

I understand that this citation refers to the kernel microflows tables. the kernel megaflows table *can be* pre-populated. Correct ? Sara On Mon, Aug 14, 2017 at 9:31 AM, Sara Gittlin wrote: > Thanks you Joe > the following citation is in a contradiction to the idea of