On 10/07/2018 13:53, Eelco Chaudron wrote:
>
>
> On 10 Jul 2018, at 14:48, Lam, Tiago wrote:
>
[snip]
>>
>> A blatant leftover from the rebase. Thanks, Eelco.
>>
>> I'll wait for Ian's reply in patch 01/15 and take this into account
>> for v5.
>>
>> Tiago.
>
> I’m on PTO starting tomorrow
On 10 Jul 2018, at 14:48, Lam, Tiago wrote:
On 10/07/2018 13:40, Ilya Maximets wrote:
On 10.07.2018 15:30, Eelco Chaudron wrote:
On 10 Jul 2018, at 13:06, Tiago Lam wrote:
From: Mark Kavanagh
Currently, jumbo frame support for OvS-DPDK is implemented by
increasing the size of mbufs
On 10/07/2018 13:40, Ilya Maximets wrote:
> On 10.07.2018 15:30, Eelco Chaudron wrote:
>>
>>
>> On 10 Jul 2018, at 13:06, Tiago Lam wrote:
>>
>>> From: Mark Kavanagh
>>>
>>> Currently, jumbo frame support for OvS-DPDK is implemented by
>>> increasing the size of mbufs within a mempool, such that
On 7/10/2018 1:40 PM, Ilya Maximets wrote:
On 10.07.2018 15:30, Eelco Chaudron wrote:
On 10 Jul 2018, at 13:06, Tiago Lam wrote:
From: Mark Kavanagh
Currently, jumbo frame support for OvS-DPDK is implemented by
increasing the size of mbufs within a mempool, such that each mbuf
within the
On 10.07.2018 15:30, Eelco Chaudron wrote:
>
>
> On 10 Jul 2018, at 13:06, Tiago Lam wrote:
>
>> From: Mark Kavanagh
>>
>> Currently, jumbo frame support for OvS-DPDK is implemented by
>> increasing the size of mbufs within a mempool, such that each mbuf
>> within the pool is large enough to
On 10 Jul 2018, at 13:06, Tiago Lam wrote:
From: Mark Kavanagh
Currently, jumbo frame support for OvS-DPDK is implemented by
increasing the size of mbufs within a mempool, such that each mbuf
within the pool is large enough to contain an entire jumbo frame of
a user-defined size.
