| Message ID | 1647542252-35727-2-git-send-email-nicolas.chautru@intel.com (mailing list archive) |
|---|---|
| State | Superseded |
| Delegated to: | Thomas Monjalon |
| Headers | show |
| Series | [v2] doc: announce changes in bbdev related to enum extension | expand |
| Context | Check | Description |
|---|---|---|
| ci/iol-broadcom-Functional | fail | Functional Testing issues |
| ci/iol-x86_64-unit-testing | success | Testing PASS |
| ci/iol-x86_64-compile-testing | success | Testing PASS |
| ci/github-robot: build | success | github build: passed |
| ci/iol-aarch64-compile-testing | success | Testing PASS |
| ci/iol-intel-Functional | success | Functional Testing PASS |
| ci/iol-intel-Performance | success | Performance Testing PASS |
| ci/iol-mellanox-Performance | success | Performance Testing PASS |
| ci/iol-aarch64-unit-testing | success | Testing PASS |
| ci/intel-Testing | success | Testing PASS |
| ci/Intel-compilation | success | Compilation OK |
| ci/checkpatch | success | coding style OK |
v3: being more explicit wrt the list of intended changes for 22.11 v2: indentation fix Realizing when submitting new bbdev operation in this patch (https://patchwork.dpdk.org/project/dpdk/list/?series=22111) that this is not workable in practice to extend this API into 22.07 without fundamental ABI breakage even by using existing versionning framework. Some existing learnings to be applied here to prevent extension being blocked, hence accouncing changes in bbdev intended for 22.11 to make this more future-proof, including dropping max value from enum, as well as deferring extension of the API for FFT operation into DPDK 22.11. Let me know if any comments or in case this should be captured differently. Thanks Nic Nicolas Chautru (1): doc: announce changes in bbdev related to enum extension doc/guides/rel_notes/deprecation.rst | 10 ++++++++++ 1 file changed, 10 insertions(+)
v4: correcting typo. Hemant, Maxime kindly review/ack. v3: being more explicit wrt the list of intended changes for 22.11 v2: indentation fix Realizing when submitting new bbdev operation in this patch (https://patchwork.dpdk.org/project/dpdk/list/?series=22111) that this is not workable in practice to extend this API into 22.07 without fundamental ABI breakage even by using existing versionning framework. Some existing learnings to be applied here to prevent extension being blocked, hence accouncing changes in bbdev intended for 22.11 to make this more future-proof, including dropping max value from enum, as well as deferring extension of the API for FFT operation into DPDK 22.11. Let me know if any comments or in case this should be captured differently. Thanks Nic Nicolas Chautru (1): doc: announce changes in bbdev related to enum extension doc/guides/rel_notes/deprecation.rst | 11 +++++++++++ 1 file changed, 11 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 4e5b23c..ff161c5 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -112,6 +112,14 @@ Deprecation Notices session and the private data of session. An opaque pointer can be exposed directly to application which can be attached to the ``rte_crypto_op``. +* bbdev: Will fix extending some enum breaking the ABI. Notably + deprecating ``RTE_BBDEV_OP_TYPE_COUNT`` terminating the ``rte_bbdev_op_type`` + and use fixed array size when required to allow for future enum extension. + Will also remove some of the inlining when causing ABI future-proof concerns. + Will extend API to support new operation type ``RTE_BBDEV_OP_FFT`` as per this + RFC https://patchwork.dpdk.org/project/dpdk/list/?series=22111 + This should be updated in DPDK 22.11. + * security: Hide structure ``rte_security_session`` and expose an opaque pointer for the private data to the application which can be attached to the packet while enqueuing.
Intent to resolve in DPDK 22.11 historical usage which prevents graceful extension of enum and API without troublesome ABI breakage as well as extending API RTE_BBDEV_OP_FFT for new operation type in bbdev. Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com> --- doc/guides/rel_notes/deprecation.rst | 8 ++++++++ 1 file changed, 8 insertions(+)