> -----Original Message----- > From: Ferruh Yigit [mailto:ferruh.yi...@intel.com] > Sent: Tuesday, April 10, 2018 5:31 PM > To: Ophir Munk <ophi...@mellanox.com>; dev@dpdk.org; Pascal Mazon > <pascal.ma...@6wind.com> > Cc: Thomas Monjalon <tho...@monjalon.net>; Olga Shern > <ol...@mellanox.com> > Subject: Re: [dpdk-dev] [RFC 0/2] TAP TSO Implementation > > On 4/9/2018 11:37 PM, Ophir Munk wrote: > > 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 <ophi...@mellanox.com>; dev@dpdk.org; Pascal Mazon > >> <pascal.ma...@6wind.com> > >> Cc: Thomas Monjalon <tho...@monjalon.net>; Olga Shern > >> <ol...@mellanox.com> > >> 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_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 be > >>> used as a failsafe sub device and be paired with another PCI device > >>> which supports TSO capability in HW. > >>> > >>> This RFC includes 2 commits: > >>> 1. Calculation of IP/TCP/UDP checksums for multi segments packets. > >>> Previously checksum offload was skipped if the number of packet > >>> segments was greater than 1. > >>> This commit removes this limitation. It is required before > >>> supporting TAP TSO since the generated small TCP packets may be > >>> composed by themselves by more than one segment. > >>> 2. Core TAP TSO implementation: calling rte_gso_segment() segments > >>> large TCP packets. > >>> To be added: creation of a small private mbuf pool in TAP required > >>> by > >> librte_gso. > >>> The number of buffers will be 64 - each of 128 bytes length. > >>> > >>> Ophir Munk (2): > >>> net/tap: calculate checksum for multi segs packets > >>> net/tap: implement TAP TSO > >> > >> This is an RFC, and V1 not sent for the patch, is this still valid > >> for this release or should we push into next one? > > > > V1 was sent for this release: > > > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdpd > > > k.org%2Fdev%2Fpatchwork%2Fpatch%2F37757%2F&data=02%7C01%7Coph > irmu%40me > > > llanox.com%7C057123ad0d0f4109362e08d59eefabc4%7Ca652971c7d2e4d9 > ba6a4d1 > > > 49256f461b%7C0%7C0%7C636589674583274060&sdata=Bumv4gojSyz6QRC > yVI7n3HJA > > qS%2FZwKRICghcndKu3is%3D&reserved=0 > > "was sent" :) that patch is same date with this mail...
I hope it has an earlier delivery time though... :)
