> -Original Message-
> From: Ferruh Yigit [mailto:ferruh.yi...@intel.com]
> Sent: Tuesday, April 10, 2018 5:31 PM
> To: Ophir Munk ; dev@dpdk.org; Pascal Mazon
>
> Cc: Thomas Monjalon ; Olga Shern
>
> Subject: Re: [dpdk-dev] [RFC 0/2] TAP TSO Implementation
&
>> Cc: Thomas Monjalon ; Olga Shern
>>
>> Subject: Re: [dpdk-dev] [RFC 0/2] TAP TSO Implementation
>>
>> On 3/9/2018 9:10 PM, Ophir Munk wrote:
>>> This RFC suggests TAP TSO (TSP segmentation offload) implementation in
>> SW.
>>> It uses dpdk library rte_gs
Patch sent for this release.
> -Original Message-
> From: Ferruh Yigit [mailto:ferruh.yi...@intel.com]
> Sent: Monday, April 09, 2018 7:39 PM
> To: Ophir Munk ; dev@dpdk.org; Pascal Mazon
>
> Cc: Thomas Monjalon ; Olga Shern
>
> Subject: Re: [dpdk-dev] [RFC 0/2
On 3/9/2018 9:10 PM, Ophir Munk wrote:
> This RFC suggests TAP TSO (TSP segmentation offload) implementation in SW.
> It uses dpdk library rte_gso which is also used by testpmd.
> Dpdk rte_gso library segments large TCP payloads (e.g. 64K bytes)
> into smaller MTU size buffers.
> By supporting TSO
This RFC suggests TAP TSO (TSP segmentation offload) implementation in SW.
It uses dpdk library rte_gso which is also used by testpmd.
Dpdk rte_gso library segments large TCP payloads (e.g. 64K bytes)
into smaller MTU size buffers.
By supporting TSO offload capability in software a TAP device can b
5 matches
Mail list logo