>>
>>
>> +/* Metadata. */
>> if (md) {
>> -flow->tunnel = md->tunnel;
>> -flow->in_port = md->in_port;
>> -flow->skb_priority = md->skb_priority;
>> -flow->pkt_mark = md->pkt_mark;
>> -flow->recirc_id = md->recirc_id;
>> -flow->dp_hash = md
Hi Jarno,
Quick question..
On 18 April 2014 13:36, Jarno Rajahalme wrote:
> miniflow_extract() extracts packet headers directly to a miniflow,
> which is a compressed form of the struct flow. This does not require
> a large struct to be cleared to begin with, and accesses less memory.
> These
Pushed, thanks for the prompt review!
Jarno
On Apr 18, 2014, at 2:32 AM, YAMAMOTO Takashi wrote:
>> miniflow_extract() extracts packet headers directly to a miniflow,
>> which is a compressed form of the struct flow. This does not require
>> a large struct to be cleared to begin with, and ac
> miniflow_extract() extracts packet headers directly to a miniflow,
> which is a compressed form of the struct flow. This does not require
> a large struct to be cleared to begin with, and accesses less memory.
> These performance benefits should allow this to be used in the DPDK
> datapath.
>
>
miniflow_extract() extracts packet headers directly to a miniflow,
which is a compressed form of the struct flow. This does not require
a large struct to be cleared to begin with, and accesses less memory.
These performance benefits should allow this to be used in the DPDK
datapath.
miniflow_extr
