>>
>>
>>How about something like this ?
>>
>>+ * Each struct has its own flow cache and classifier per managed inport.
>>Packets
>>+ *received from managed ports are looked up in the corresponding pmd
>>+ * thread's flow cache and corresponding classifier, if the flow
>>cache misses.
>>
>
>
>How about something like this ?
>
>+ * Each struct has its own flow cache and classifier per managed inport.
>Packets
>+ *received from managed ports are looked up in the corresponding pmd
>+ * thread's flow cache and corresponding classifier, if the flow cache
>misses.
>+ * Pa
On Tue, Apr 18, 2017 at 07:13:26PM +, Bodireddy, Bhanuprakash wrote:
> >On Sun, Mar 12, 2017 at 05:33:27PM +, Bhanuprakash Bodireddy wrote:
> >> The sorted subtable ranking patch introduced a classifier instance per
> >> ingress port with its subtables ranked on the frequency of hits. The
>
On 3/12/17, 10:33 AM, "ovs-dev-boun...@openvswitch.org on behalf of
Bhanuprakash Bodireddy" wrote:
The sorted subtable ranking patch introduced a classifier instance per
ingress port with its subtables ranked on the frequency of hits. The pmd
thread can have more classifier instanc
>On Sun, Mar 12, 2017 at 05:33:27PM +, Bhanuprakash Bodireddy wrote:
>> The sorted subtable ranking patch introduced a classifier instance per
>> ingress port with its subtables ranked on the frequency of hits. The
>> pmd thread can have more classifier instances now and solely depends
>> on th
On Sun, Mar 12, 2017 at 05:33:27PM +, Bhanuprakash Bodireddy wrote:
> The sorted subtable ranking patch introduced a classifier instance per
> ingress port with its subtables ranked on the frequency of hits. The pmd
> thread can have more classifier instances now and solely depends on the
> num
The sorted subtable ranking patch introduced a classifier instance per
ingress port with its subtables ranked on the frequency of hits. The pmd
thread can have more classifier instances now and solely depends on the
number of ingress ports currently handled by the pmd thread.
Signed-off-by: Bhanup
