Re: [PATCH net-next v2 2/2] openvswitch: Support conntrack zone limit

2018-04-27 Thread Pravin Shelar
On Wed, Apr 25, 2018 at 2:51 PM, Yi-Hung Wei wrote: >>> +#ifIS_ENABLED(CONFIG_NETFILTER_CONNCOUNT) >>> +#define OVS_CT_LIMIT_UNLIMITED 0 >>> +#define OVS_CT_LIMIT_DEFAULT OVS_CT_LIMIT_UNLIMITED >>> +#define CT_LIMIT_HASH_BUCKETS 512 >>> + >> Can you use static key when the limit is not set. >>

Re: [PATCH net-next v2 2/2] openvswitch: Support conntrack zone limit

2018-04-25 Thread Yi-Hung Wei
>> +#ifIS_ENABLED(CONFIG_NETFILTER_CONNCOUNT) >> +#define OVS_CT_LIMIT_UNLIMITED 0 >> +#define OVS_CT_LIMIT_DEFAULT OVS_CT_LIMIT_UNLIMITED >> +#define CT_LIMIT_HASH_BUCKETS 512 >> + > Can you use static key when the limit is not set. > This would avoid overhead in datapath when these limits are

Re: [PATCH net-next v2 2/2] openvswitch: Support conntrack zone limit

2018-04-23 Thread Pravin Shelar
On Tue, Apr 17, 2018 at 5:30 PM, Yi-Hung Wei wrote: > Currently, nf_conntrack_max is used to limit the maximum number of > conntrack entries in the conntrack table for every network namespace. > For the VMs and containers that reside in the same namespace, > they share the same conntrack table, an

[PATCH net-next v2 2/2] openvswitch: Support conntrack zone limit

2018-04-17 Thread Yi-Hung Wei
Currently, nf_conntrack_max is used to limit the maximum number of conntrack entries in the conntrack table for every network namespace. For the VMs and containers that reside in the same namespace, they share the same conntrack table, and the total # of conntrack entries for all the VMs and contai