d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
fe16d678e7
numam-dpdk/lib/librte_pipeline/version.map

119 lines
3.4 KiB
Plaintext
Raw Normal View History

version: 20.11-rc0 Start a new release cycle with empty release notes. The ABI version becomes 21.0. The ABI major is back to normal, having only one number (21 vs 20.0). The map files are updated to the new ABI major number (21). The ABI exceptions are dropped. Travis ABI check is disabled because compatibility is not preserved. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Ray Kinsella <mdr@ashroe.eu>
2020-08-10 15:10:20 +00:00
DPDK_21 {
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
global:
build: align symbols with global ABI version Merge all versions in linker version script files to DPDK_20.0. This commit was generated by running the following command: :~/DPDK$ buildtools/update-abi.sh 20.0 Signed-off-by: Pawel Modrak <pawelx.modrak@intel.com> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-11-20 17:23:38 +00:00
rte_pipeline_ah_packet_drop;
rte_pipeline_ah_packet_hijack;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_pipeline_check;
rte_pipeline_create;
rte_pipeline_flush;
rte_pipeline_free;
rte_pipeline_port_in_connect_to_table;
rte_pipeline_port_in_create;
rte_pipeline_port_in_disable;
rte_pipeline_port_in_enable;
build: align symbols with global ABI version Merge all versions in linker version script files to DPDK_20.0. This commit was generated by running the following command: :~/DPDK$ buildtools/update-abi.sh 20.0 Signed-off-by: Pawel Modrak <pawelx.modrak@intel.com> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-11-20 17:23:38 +00:00
rte_pipeline_port_in_stats_read;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_pipeline_port_out_create;
rte_pipeline_port_out_packet_insert;
build: align symbols with global ABI version Merge all versions in linker version script files to DPDK_20.0. This commit was generated by running the following command: :~/DPDK$ buildtools/update-abi.sh 20.0 Signed-off-by: Pawel Modrak <pawelx.modrak@intel.com> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-11-20 17:23:38 +00:00
rte_pipeline_port_out_stats_read;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_pipeline_run;
rte_pipeline_table_create;
rte_pipeline_table_default_entry_add;
rte_pipeline_table_default_entry_delete;
rte_pipeline_table_entry_add;
build: align symbols with global ABI version Merge all versions in linker version script files to DPDK_20.0. This commit was generated by running the following command: :~/DPDK$ buildtools/update-abi.sh 20.0 Signed-off-by: Pawel Modrak <pawelx.modrak@intel.com> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-11-20 17:23:38 +00:00
rte_pipeline_table_entry_add_bulk;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
rte_pipeline_table_entry_delete;
build: align symbols with global ABI version Merge all versions in linker version script files to DPDK_20.0. This commit was generated by running the following command: :~/DPDK$ buildtools/update-abi.sh 20.0 Signed-off-by: Pawel Modrak <pawelx.modrak@intel.com> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-11-20 17:23:38 +00:00
rte_pipeline_table_entry_delete_bulk;
rte_pipeline_table_stats_read;
lib: provide initial versioning Add linker version script files to each DPDK library to put a stake in the ground from which we can start cleaning up API's Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-02-02 17:40:20 +00:00
local: *;
};
pipeline: fix missing exported symbols Exported symbols for port in, port out and table stats. Fixes: 6504bb5ec460 ("pipeline: add statistics for ports and tables") Signed-off-by: Maciej Gajdzica <maciejx.t.gajdzica@intel.com> Acked-by: Michal Jastrzebski <michalx.k.jastrzebski@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2015-07-09 08:17:10 +00:00
pipeline: add table action APIs This API provides a common set of actions for pipeline tables to speed up application development. Each match-action rule added to a pipeline table has associated data that stores the action context. This data is input to the table action handler called for every input packet that hits the rule as part of the table lookup during the pipeline execution. The pipeline library allows the user to define his own table actions by providing customized table action handlers (table lookup) and complete freedom of setting the rules and their data (table rule add/delete). While the user can still follow this process, this API is intended to provide a quicker development alternative for a set of predefined actions. The typical steps to use this API are: * Define a table action profile. * Instantiate the table action profile to create table action objects. * Use the table action object to generate the pipeline table action handlers (invoked by the pipeline table lookup operation). * Use the table action object to generate the rule data (for the pipeline table rule add operation) based on given action parameters. * Use the table action object to read action data (e.g. stats counters) for any given rule. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:20 +00:00
EXPERIMENTAL {
global:
pipeline: add new SWX pipeline type Add new improved Software Switch (SWX) pipeline type that supports dynamically-defined packet headers, meta-data, actions and pipelines. Actions and pipelines are defined through instructions. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:29 +00:00
# added in 18.05
pipeline: add port in action APIs This API provides a common set of actions for pipeline input ports to speed up application development. Each pipeline input port can be assigned an action handler to be executed on every input packet during the pipeline execution. The pipeline library allows the user to define his own input port actions by providing customized input port action handler. While the user can still follow this process, this API is intended to provide a quicker development alternative for a set of predefined actions. The typical steps to use this API are: * Define an input port action profile. * Instantiate the input port action profile to create input port action objects. * Use the input port action to generate the input port action handler invoked by the pipeline. * Use the input port action object to generate the internal data structures used by the input port action handler based on given action parameters. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:30 +00:00
rte_port_in_action_apply;
rte_port_in_action_create;
rte_port_in_action_free;
rte_port_in_action_params_get;
rte_port_in_action_profile_action_register;
rte_port_in_action_profile_create;
rte_port_in_action_profile_free;
rte_port_in_action_profile_freeze;
pipeline: add table action APIs This API provides a common set of actions for pipeline tables to speed up application development. Each match-action rule added to a pipeline table has associated data that stores the action context. This data is input to the table action handler called for every input packet that hits the rule as part of the table lookup during the pipeline execution. The pipeline library allows the user to define his own table actions by providing customized table action handlers (table lookup) and complete freedom of setting the rules and their data (table rule add/delete). While the user can still follow this process, this API is intended to provide a quicker development alternative for a set of predefined actions. The typical steps to use this API are: * Define a table action profile. * Instantiate the table action profile to create table action objects. * Use the table action object to generate the pipeline table action handlers (invoked by the pipeline table lookup operation). * Use the table action object to generate the rule data (for the pipeline table rule add operation) based on given action parameters. * Use the table action object to read action data (e.g. stats counters) for any given rule. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:20 +00:00
rte_table_action_apply;
rte_table_action_create;
pipeline: add traffic metering action Add traffic metering action implementation. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:22 +00:00
rte_table_action_dscp_table_update;
pipeline: add table action APIs This API provides a common set of actions for pipeline tables to speed up application development. Each match-action rule added to a pipeline table has associated data that stores the action context. This data is input to the table action handler called for every input packet that hits the rule as part of the table lookup during the pipeline execution. The pipeline library allows the user to define his own table actions by providing customized table action handlers (table lookup) and complete freedom of setting the rules and their data (table rule add/delete). While the user can still follow this process, this API is intended to provide a quicker development alternative for a set of predefined actions. The typical steps to use this API are: * Define a table action profile. * Instantiate the table action profile to create table action objects. * Use the table action object to generate the pipeline table action handlers (invoked by the pipeline table lookup operation). * Use the table action object to generate the rule data (for the pipeline table rule add operation) based on given action parameters. * Use the table action object to read action data (e.g. stats counters) for any given rule. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:20 +00:00
rte_table_action_free;
pipeline: add traffic metering action Add traffic metering action implementation. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:22 +00:00
rte_table_action_meter_profile_add;
rte_table_action_meter_profile_delete;
rte_table_action_meter_read;
pipeline: add table action APIs This API provides a common set of actions for pipeline tables to speed up application development. Each match-action rule added to a pipeline table has associated data that stores the action context. This data is input to the table action handler called for every input packet that hits the rule as part of the table lookup during the pipeline execution. The pipeline library allows the user to define his own table actions by providing customized table action handlers (table lookup) and complete freedom of setting the rules and their data (table rule add/delete). While the user can still follow this process, this API is intended to provide a quicker development alternative for a set of predefined actions. The typical steps to use this API are: * Define a table action profile. * Instantiate the table action profile to create table action objects. * Use the table action object to generate the pipeline table action handlers (invoked by the pipeline table lookup operation). * Use the table action object to generate the rule data (for the pipeline table rule add operation) based on given action parameters. * Use the table action object to read action data (e.g. stats counters) for any given rule. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:20 +00:00
rte_table_action_profile_action_register;
rte_table_action_profile_create;
rte_table_action_profile_free;
rte_table_action_profile_freeze;
pipeline: add statistics read action Add implementation of stats read action Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:27 +00:00
rte_table_action_stats_read;
pipeline: add new SWX pipeline type Add new improved Software Switch (SWX) pipeline type that supports dynamically-defined packet headers, meta-data, actions and pipelines. Actions and pipelines are defined through instructions. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:29 +00:00
rte_table_action_table_params_get;
pipeline: add timestamp action Add implementation of timestamp action. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:28 +00:00
rte_table_action_time_read;
pipeline: add TTL update action Add implementation of ttl update action. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-03-29 18:31:26 +00:00
rte_table_action_ttl_read;
pipeline: add new SWX pipeline type Add new improved Software Switch (SWX) pipeline type that supports dynamically-defined packet headers, meta-data, actions and pipelines. Actions and pipelines are defined through instructions. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:29 +00:00
# added in 18.11
pipeline: add symmetric crypto table action This patch adds the symmetric crypto action support to pipeline library. The symmetric crypto action works as the shim layer between pipeline and DPDK cryptodev and is able to interact with cryptodev with the control path requests such as session creation/deletion and data path work to assemble the crypto operations for received packets. Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2018-09-28 12:26:09 +00:00
rte_table_action_crypto_sym_session_get;
pipeline: add new SWX pipeline type Add new improved Software Switch (SWX) pipeline type that supports dynamically-defined packet headers, meta-data, actions and pipelines. Actions and pipelines are defined through instructions. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:29 +00:00
# added in 20.11
pipeline: add SWX pipeline query API Query API to be used by the control plane to detect the configuration and state of the SWX pipeline and its internal objects. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:57 +00:00
rte_swx_ctl_action_arg_info_get;
rte_swx_ctl_action_info_get;
pipeline: add SWX table update high level API High-level transaction-oriented API for SWX pipeline table updates. It supports multi-table atomic updates, i.e. multiple tables can be updated in a single step with only the before and after table set visible to the packets. Uses the lower-level table update mechanisms. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:59 +00:00
rte_swx_ctl_pipeline_abort;
rte_swx_ctl_pipeline_commit;
rte_swx_ctl_pipeline_create;
rte_swx_ctl_pipeline_free;
pipeline: add SWX pipeline query API Query API to be used by the control plane to detect the configuration and state of the SWX pipeline and its internal objects. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:57 +00:00
rte_swx_ctl_pipeline_info_get;
rte_swx_ctl_pipeline_numa_node_get;
rte_swx_ctl_pipeline_port_in_stats_read;
rte_swx_ctl_pipeline_port_out_stats_read;
pipeline: add SWX table update high level API High-level transaction-oriented API for SWX pipeline table updates. It supports multi-table atomic updates, i.e. multiple tables can be updated in a single step with only the before and after table set visible to the packets. Uses the lower-level table update mechanisms. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:59 +00:00
rte_swx_ctl_pipeline_table_default_entry_add;
rte_swx_ctl_pipeline_table_entry_add;
rte_swx_ctl_pipeline_table_entry_delete;
rte_swx_ctl_pipeline_table_entry_read;
rte_swx_ctl_pipeline_table_fprintf;
pipeline: add SWX pipeline query API Query API to be used by the control plane to detect the configuration and state of the SWX pipeline and its internal objects. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:57 +00:00
rte_swx_ctl_table_action_info_get;
rte_swx_ctl_table_info_get;
rte_swx_ctl_table_match_field_info_get;
rte_swx_ctl_table_ops_get;
pipeline: add SWX pipeline action Add SWX actions that are dynamically-defined through instructions as opposed to pre-defined. The actions are subroutines of the pipeline program that triggered by table lookup. The input arguments are the action data from the table entry (format defined by struct), the headers and meta-data are in/out. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:34 +00:00
rte_swx_pipeline_action_config;
pipeline: add new SWX pipeline type Add new improved Software Switch (SWX) pipeline type that supports dynamically-defined packet headers, meta-data, actions and pipelines. Actions and pipelines are defined through instructions. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:29 +00:00
rte_swx_pipeline_build;
pipeline: add SWX pipeline specification file Add support for building the SWX pipeline based on specification file with syntax aligned to the P4 language. The specification file may be generated by the P4C compiler in the future. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:20:00 +00:00
rte_swx_pipeline_build_from_spec;
pipeline: add new SWX pipeline type Add new improved Software Switch (SWX) pipeline type that supports dynamically-defined packet headers, meta-data, actions and pipelines. Actions and pipelines are defined through instructions. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:29 +00:00
rte_swx_pipeline_config;
pipeline: add SWX extern objects and funcs Add extern objects and functions to plug into the SWX pipeline any functionality that cannot be efficiently implemented with existing instructions, e.g. special checksum/ECC, crypto, meters, stats arrays, heuristics, etc. In/out arguments are passed through mailbox with format defined by struct. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:33 +00:00
rte_swx_pipeline_extern_func_register;
rte_swx_pipeline_extern_object_config;
rte_swx_pipeline_extern_type_member_func_register;
rte_swx_pipeline_extern_type_register;
pipeline: add SWX pipeline flush Flush the packets currently buffered by the SWX pipeline output ports. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:58 +00:00
rte_swx_pipeline_flush;
pipeline: add new SWX pipeline type Add new improved Software Switch (SWX) pipeline type that supports dynamically-defined packet headers, meta-data, actions and pipelines. Actions and pipelines are defined through instructions. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:29 +00:00
rte_swx_pipeline_free;
pipeline: add SWX pipeline instructions The SWX pipeline instructions represent the main program that defines the life of the packet. As packets go through tables that trigger action subroutines, the headers and meta-data get transformed along the way. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:36 +00:00
rte_swx_pipeline_instructions_config;
pipeline: add SWX headers and meta-data Add support for dynamically-defined packet headers and meta-data to the SWX pipeline. The header and meta-data format are defined by the struct type they instantiate. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:32 +00:00
rte_swx_pipeline_packet_header_register;
rte_swx_pipeline_packet_metadata_register;
pipeline: add SWX pipeline input port Add input ports to the newly introduced SWX pipeline type. Each port instantiates a port type that defines the port operations, e.g. ethdev port, PCAP port, etc. The RX interface is single packet, with packet batching internally for performance. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:30 +00:00
rte_swx_pipeline_port_in_config;
rte_swx_pipeline_port_in_type_register;
pipeline: add SWX pipeline output port Add output ports to the newly introduced SWX pipeline type. Each port instantiates a port type that defines the port operations, e.g. ethdev port, PCAP port, etc. The TX interface is single packet, with packet batching internally for performance. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:31 +00:00
rte_swx_pipeline_port_out_config;
rte_swx_pipeline_port_out_type_register;
pipeline: add SWX Rx and extract instructions Add packet reception and header extraction instructions. The Rx must be the first pipeline instruction. Each extracted header is logically removed from the packet, then it can be read/written by instructions, emitted into the outgoing packet or discarded. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:37 +00:00
rte_swx_pipeline_run;
pipeline: add SWX headers and meta-data Add support for dynamically-defined packet headers and meta-data to the SWX pipeline. The header and meta-data format are defined by the struct type they instantiate. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:32 +00:00
rte_swx_pipeline_struct_type_register;
pipeline: add SWX pipeline tables Add tables to the SWX pipeline. The match fields are flexibly selected from the headers and meta-data. The set of table actions is flexibly selected for each table from the set of pipeline actions. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-10-01 10:19:35 +00:00
rte_swx_pipeline_table_config;
rte_swx_pipeline_table_state_get;
rte_swx_pipeline_table_state_set;
rte_swx_pipeline_table_type_register;
pipeline: add register array to SWX Register arrays are stateful objects that can be read & modified by both the data plane and the control plane, as opposed to tables, which are read-only for data plane. One key use-case is the implementation of stats counters. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2021-03-16 11:40:38 +00:00
#added in 21.05
pipeline: add meter array to SWX Meter arrays are stateful objects that are updated by the data plane and configured & monitored by the control plane. The meters implement the RFC 2698 Two Rate Three Color Marker (trTCM) algorithm. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2021-03-16 11:40:39 +00:00
rte_swx_ctl_metarray_info_get;
rte_swx_ctl_meter_profile_add;
rte_swx_ctl_meter_profile_delete;
rte_swx_ctl_meter_reset;
rte_swx_ctl_meter_set;
rte_swx_ctl_meter_stats_read;
pipeline: add register array to SWX Register arrays are stateful objects that can be read & modified by both the data plane and the control plane, as opposed to tables, which are read-only for data plane. One key use-case is the implementation of stats counters. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2021-03-16 11:40:38 +00:00
rte_swx_ctl_pipeline_regarray_read;
rte_swx_ctl_pipeline_regarray_write;
rte_swx_ctl_regarray_info_get;
pipeline: add meter array to SWX Meter arrays are stateful objects that are updated by the data plane and configured & monitored by the control plane. The meters implement the RFC 2698 Two Rate Three Color Marker (trTCM) algorithm. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2021-03-16 11:40:39 +00:00
rte_swx_pipeline_metarray_config;
pipeline: add register array to SWX Register arrays are stateful objects that can be read & modified by both the data plane and the control plane, as opposed to tables, which are read-only for data plane. One key use-case is the implementation of stats counters. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2021-03-16 11:40:38 +00:00
rte_swx_pipeline_regarray_config;
lib: clear experimental version tag in linker scripts Remove version tag from experimental block in linker version scripts (.map files). That label is not used by linker and information only. It is useful for version blocks but not useful for experimental block but confusing. Removing those labels. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2018-04-27 15:17:55 +00:00
};
Reference in New Issue Copy Permalink