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
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)
**
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:
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:
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)
**
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
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)
**
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
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:
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
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
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
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
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
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
---
/**
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
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:
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
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
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
20 matches
Mail list logo