numam-dpdk/devtools/libabigail.abignore

[suppress_function]
        symbol_version = EXPERIMENTAL
[suppress_variable]
        symbol_version = EXPERIMENTAL

; Explicit ignore for driver-only ABI
[suppress_type]
        name = rte_cryptodev_ops
; Ignore this enum update as it is part of an experimental API
[suppress_type]
        type_kind = enum
        name = rte_crypto_asym_xform_type
        changed_enumerators = RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END
; Ignore updates of ring prod/cons
[suppress_type]
        type_kind = struct
        name = rte_ring
[suppress_type]
        type_kind = struct
        name = rte_event_ring
devtools: add ABI checks For normal developers, those checks are disabled. Enabling them requires a configuration that will trigger the ABI dumps generation as part of the existing devtools/test-build.sh and devtools/test-meson-builds.sh scripts. Those checks are enabled in the CI for the default meson options on x86 and aarch64 so that proposed patches are validated via our CI robot. A cache of the ABI is stored in travis jobs to avoid rebuilding too often. Checks can be informational only, by setting ABI_CHECKS_WARN_ONLY when breaking the ABI in a future release. Explicit suppression rules have been added on internal structures exposed to crypto drivers as the current ABI policy does not apply to them. This could be improved in the future by carefully splitting the headers content with application and driver "users" in mind. We currently have issues reported for librte_crypto recent changes for which suppression rules have been added too. Mellanox glue libraries are explicitly skipped as they are not part of the application ABI. Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Luca Boccassi <bluca@debian.org> 2020-02-02 21:08:34 +00:00			`[suppress_function]`
			`symbol_version = EXPERIMENTAL`
			`[suppress_variable]`
			`symbol_version = EXPERIMENTAL`

			`; Explicit ignore for driver-only ABI`
			`[suppress_type]`
			`name = rte_cryptodev_ops`
			`; Ignore this enum update as it is part of an experimental API`
			`[suppress_type]`
			`type_kind = enum`
			`name = rte_crypto_asym_xform_type`
			`changed_enumerators = RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END`
ring: introduce RTS ring mode Introduce relaxed tail sync (RTS) mode for MT ring synchronization. Aim to reduce stall times in case when ring is used on overcommited cpus (multiple active threads on the same cpu). The main difference from original MP/MC algorithm is that tail value is increased not by every thread that finished enqueue/dequeue, but only by the last one. That allows threads to avoid spinning on ring tail value, leaving actual tail value change to the last thread in the update queue. Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> 2020-04-20 12:28:24 +00:00			`; Ignore updates of ring prod/cons`
			`[suppress_type]`
			`type_kind = struct`
			`name = rte_ring`
			`[suppress_type]`
			`type_kind = struct`
			`name = rte_event_ring`