[ovs-dev] [PATCH v8 12/13] netdev-dpdk: support multi-segment jumbo frames

Lam, Tiago tiago.lam at intel.com
Fri Jun 22 19:05:15 UTC 2018


On 18/06/2018 14:16, Eelco Chaudron wrote:
> 
> 
> On 11 Jun 2018, at 18:21, Tiago Lam wrote:
> 
>> From: Mark Kavanagh <mark.b.kavanagh at intel.com>
>>

[snip]

>>
>> diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
>> index 1e27a02..cbe4650 100644
>> --- a/vswitchd/vswitch.xml
>> +++ b/vswitchd/vswitch.xml
>> @@ -331,6 +331,26 @@
>>          </p>
>>        </column>
>>
>> +      <column name="other_config" key="dpdk-multi-seg-mbufs"
>> +              type='{"type": "boolean"}'>
>> +        <p>
>> +          Specifies if DPDK uses multi-segment mbufs for handling 
>> jumbo frames.
>> +        </p>
>> +        <p>
>> +            If true, DPDK allocates a single mempool per port, 
>> irrespective
>> +            of the ports' requested MTU sizes. The elements of this 
>> mempool are
>> +            'standard'-sized mbufs (typically 2k MB), which may be 
>> chained
>> +            together to accommodate jumbo frames. In this approach, 
>> each mbuf
>> +            typically stores a fragment of the overall jumbo frame.
>> +        </p>
>> +        <p>
>> +            If not specified, defaults to <code>false</code>, in 
>> which case,
>> +            the size of each mbuf within a DPDK port's mempool will 
>> be grown to
>> +            accommodate jumbo frames within a single mbuf.
> 
> Maybe add a note that you need to restart OVS before any change becomes 
> active.
> 

Sounds good to me. I think it is mentioned already at some point that
these options require a restart, but it will remind the user that it
applies here as well. Will do for the next iteration.

Tiago.


More information about the dev mailing list