[lng-odp] [PATCH API-NEXT v3 2/2] api: ipsec: reuse checksum checking flags from packet API

From: Dmitry Eremin-Solenikov Reuse odp_packet_parse_chksum_t from packet API to ease passing checksum flags to packet parsing functions. Signed-off-by: Dmitry Eremin-Solenikov --- /** Email created from pull request 314

[lng-odp] [PATCH API-NEXT v3 1/2] api: packet: separate checksum check flags

From: Dmitry Eremin-Solenikov Separate union controlling different checksum checks. It will be used by IPsec API. Signed-off-by: Dmitry Eremin-Solenikov --- /** Email created from pull request 314 (lumag:ipsec-chksum) **

[lng-odp] [PATCH API-NEXT v3 0/2] IPsec checksumming API

Separate checksumming flags into separate type to be used by both packet parse and IPsec functions. github /** Email created from pull request 314 (lumag:ipsec-chksum) ** https://github.com/Linaro/odp/pull/314 ** Patch:

[lng-odp] [PATCH API-NEXT v2 0/2] IPsec checksumming API

Separate checksumming flags into separate type to be used by both packet parse and IPsec functions. github /** Email created from pull request 314 (lumag:ipsec-chksum) ** https://github.com/Linaro/odp/pull/314 ** Patch:

[lng-odp] [PATCH API-NEXT v2 1/2] api: packet: separate checksum check flags

From: Dmitry Eremin-Solenikov Separate union controlling different checksum checks. It will be used by IPsec API. Signed-off-by: Dmitry Eremin-Solenikov --- /** Email created from pull request 314 (lumag:ipsec-chksum) **

[lng-odp] [PATCH API-NEXT v2 2/2] api: ipsec: reuse checksum checking flags from packet API

From: Dmitry Eremin-Solenikov Reuse odp_packet_parse_chksum_t from packet API to ease passing checksum flags to packet parsing functions. Signed-off-by: Dmitry Eremin-Solenikov --- /** Email created from pull request 314

[lng-odp] [PATCH API-NEXT v1 1/2] api: packet: separate checksum check flags

From: Dmitry Eremin-Solenikov Separate union controlling different checksum checks. It will be used by IPsec API. Signed-off-by: Dmitry Eremin-Solenikov --- /** Email created from pull request 314 (lumag:ipsec-chksum) **

[lng-odp] [PATCH API-NEXT v1 2/2] api: ipsec: reuse checksum checking flags from packet API

From: Dmitry Eremin-Solenikov Reuse odp_packet_parse_chksum_t from packet API to ease passing checksum flags to packet parsing functions. Signed-off-by: Dmitry Eremin-Solenikov --- /** Email created from pull request 314

[lng-odp] [PATCH API-NEXT v1 0/2] IPsec checksumming API

Separate checksumming flags into separate type to be used by both packet parse and IPsec functions. github /** Email created from pull request 314 (lumag:ipsec-chksum) ** https://github.com/Linaro/odp/pull/314 ** Patch:

[lng-odp] [PATCH 2.0 v3 2/2] linux-dpdk: pool: Remove unused CONFIG_POOL_MAX_NUM

From: Honnappa Nagarahalli CONFIG_POOL_MAX_NUM is not used in linux-dpdk. Signed-off-by: Honnappa Nagarahalli Reviewed-by: Ola Liljedahl --- /** Email created from pull request 312

[lng-odp] [PATCH 2.0 v3 1/2] linux-generic: pool: allocate ring memory based on pool size

From: Honnappa Nagarahalli Adjust the size of ring based on configured number of buffers in the pool. Signed-off-by: Honnappa Nagarahalli Reviewed-by: Ola Liljedahl --- /** Email created from pull request 312

[lng-odp] [PATCH 2.0 v3 0/2] allocate ring memory based on pool size

The maximum size of the pool ring is 1M entries as it uses an array. However, the application provides the number of buffers in a pool during pool creation. Hence, the maximum pool ring size can be dynamic. github /** Email created from pull request 312

[lng-odp] VPP and ODP webinar: Event Registration 9am 11/30 PT

Dear all, You may be interested to register for a webinar 9-10am tomorrow Thursday PT. https://event.on24.com/eventRegistration/EventLobbyServlet?target= reg20.jsp=speaker=1539471=1= 58BAA4CAC57783D388386F55C1585A0D®Tag==register Bob Monkman and Bill Fischofer will give a presentation on

[lng-odp] [PATCH API-NEXT v1 4/5] test: l2fwd: add checksum offload option

From: Petri Savolainen Added option to enable checksum insertion at packet output. This can be used to test checksum offload in various packet IO combinations. Signed-off-by: Petri Savolainen --- /** Email created from pull request 313

[lng-odp] [PATCH API-NEXT v1 5/5] linux-gen: dpdk: checksum insert enabled flag

From: Petri Savolainen Added interface level flag to optimize checksum insertion checks. If checksum insertion has not been enabled, further configuration or packet level checks are not performed. Signed-off-by: Petri Savolainen --- /**

[lng-odp] [PATCH API-NEXT v1 3/5] linux-gen: dpdk: use checksum insert enable config

From: Petri Savolainen Enable checksum insertion only when requested. DPDK uses less optimized driver code (on Intel NICs at least) when any of the L4 checksum offloads is enabled. Signed-off-by: Petri Savolainen --- /** Email created

[lng-odp] [PATCH API-NEXT v1 2/5] example: generator use checksum enable

From: Petri Savolainen Use new checksum insert enable bits. Signed-off-by: Petri Savolainen --- /** Email created from pull request 313 (psavol:next-pktout-config) ** https://github.com/Linaro/odp/pull/313 ** Patch:

[lng-odp] [PATCH API-NEXT v1 1/5] api: pktio: add checksum insert enable bits

From: Petri Savolainen Added bits to control if checksum insertion is enabled / disabled at packet output. Current configuration options control if checksum is inserted / not inserted by default, but leaves it open for application to request checksum always with

[lng-odp] [PATCH API-NEXT v1 0/5] api: pktio: add checksum insert enable bits

Added bits to control if checksum insertion is enabled / disabled at packet output. Current configuration options control if checksum is inserted / not inserted by default, but leaves it open for application to request checksum always with override functions. Explicit disable allows implementation

[lng-odp] L4 offset

Hi, I'm trying to understand when pktio implementation should set the L4 offset. In point of view, if there is a known L3 header than the L4 offset should be set to the L3-offset + L3 header length. I noticed that Linux generic implementation is not as above. E.g. if there is only IP header and