[dpdk-dev] Experimental symbols in eal lib

[dpdk-dev] Experimental symbols in eal lib

[Kinsella, Ray]

Hi Anatoly & Thomas, 

The following eal experimental symbols are present in both v21.05 and v19.11 release. These symbols should be considered for promotion to stable as part of the v22 ABI in DPDK 21.11, as they have been experimental for >= 2yrs at this point. 

 * rte_mp_action_register
 * rte_mp_action_unregister
 * rte_mp_reply
 * rte_mp_sendmsg
 * rte_dev_event_callback_register
 * rte_dev_event_callback_unregister
 * rte_dev_event_monitor_start
 * rte_dev_event_monitor_stop
 * rte_fbarray_attach
 * rte_fbarray_destroy
 * rte_fbarray_detach
 * rte_fbarray_dump_metadata
 * rte_fbarray_find_contig_free
 * rte_fbarray_find_contig_used
 * rte_fbarray_find_idx
 * rte_fbarray_find_next_free
 * rte_fbarray_find_next_n_free
 * rte_fbarray_find_next_n_used
 * rte_fbarray_find_next_used
 * rte_fbarray_get
 * rte_fbarray_init
 * rte_fbarray_is_used
 * rte_fbarray_set_free
 * rte_fbarray_set_used
 * rte_log_register_type_and_pick_level
 * rte_malloc_dump_heaps
 * rte_mem_alloc_validator_register
 * rte_mem_alloc_validator_unregister
 * rte_mem_check_dma_mask
 * rte_mem_event_callback_register
 * rte_mem_event_callback_unregister
 * rte_mem_iova2virt
 * rte_mem_virt2memseg
 * rte_mem_virt2memseg_list
 * rte_memseg_contig_walk
 * rte_memseg_list_walk
 * rte_memseg_walk
 * rte_mp_request_async
 * rte_mp_request_sync
 * rte_class_find
 * rte_class_find_by_name
 * rte_class_register
 * rte_class_unregister
 * rte_dev_iterator_init
 * rte_dev_iterator_next
 * rte_fbarray_find_prev_free
 * rte_fbarray_find_prev_n_free
 * rte_fbarray_find_prev_n_used
 * rte_fbarray_find_prev_used
 * rte_fbarray_find_rev_contig_free
 * rte_fbarray_find_rev_contig_used
 * rte_memseg_contig_walk_thread_unsafe
 * rte_memseg_list_walk_thread_unsafe
 * rte_memseg_walk_thread_unsafe
 * rte_delay_us_sleep
 * rte_dev_event_callback_process
 * rte_dev_hotplug_handle_disable
 * rte_dev_hotplug_handle_enable
 * rte_malloc_heap_create
 * rte_malloc_heap_destroy
 * rte_malloc_heap_get_socket
 * rte_malloc_heap_memory_add
 * rte_malloc_heap_memory_attach
 * rte_malloc_heap_memory_detach
 * rte_malloc_heap_memory_remove
 * rte_malloc_heap_socket_is_external
 * rte_mem_check_dma_mask_thread_unsafe
 * rte_mem_set_dma_mask
 * rte_memseg_get_fd
 * rte_memseg_get_fd_offset
 * rte_memseg_get_fd_offset_thread_unsafe
 * rte_memseg_get_fd_thread_unsafe
 * rte_extmem_attach
 * rte_extmem_detach
 * rte_extmem_register
 * rte_extmem_unregister
 * rte_dev_dma_map
 * rte_dev_dma_unmap
 * rte_fbarray_find_biggest_free
 * rte_fbarray_find_biggest_used
 * rte_fbarray_find_rev_biggest_free
 * rte_fbarray_find_rev_biggest_used
 * rte_intr_callback_unregister_pending
 * rte_realloc_socket
 * rte_intr_ack
 * rte_lcore_cpuset
 * rte_lcore_to_cpu_id
 * rte_mcfg_timer_lock
 * rte_mcfg_timer_unlock
 * rte_rand_max

Ray K

Re: [dpdk-dev] Experimental symbols in eal lib

[David Marchand]

On Thu, Jun 24, 2021 at 12:31 PM Kinsella, Ray <mdr@ashroe.eu> wrote:
>
> Hi Anatoly & Thomas,
>
> The following eal experimental symbols are present in both v21.05 and v19.11 release. These symbols should be considered for promotion to stable as part of the v22 ABI in DPDK 21.11, as they have been experimental for >= 2yrs at this point.

Just an additional comment.
Marking stable is not the only choice.
We can also consider hiding such symbols (marking internal) if there
is no clear usecase out of DPDK.


-- 
David Marchand

Re: [dpdk-dev] Experimental symbols in eal lib

[Kinsella, Ray]

Good point, that one is very up to the lib maintainer to make that call.

Ray K

On 24/06/2021 13:14, David Marchand wrote:
> On Thu, Jun 24, 2021 at 12:31 PM Kinsella, Ray <mdr@ashroe.eu> wrote:
>>
>> Hi Anatoly & Thomas,
>>
>> The following eal experimental symbols are present in both v21.05 and v19.11 release. These symbols should be considered for promotion to stable as part of the v22 ABI in DPDK 21.11, as they have been experimental for >= 2yrs at this point.
> 
> Just an additional comment.
> Marking stable is not the only choice.
> We can also consider hiding such symbols (marking internal) if there
> is no clear usecase out of DPDK.
> 
> 

Re: [dpdk-dev] Experimental symbols in eal lib

[Tyler Retzlaff]

On Thu, Jun 24, 2021 at 02:14:16PM +0200, David Marchand wrote:
> On Thu, Jun 24, 2021 at 12:31 PM Kinsella, Ray <mdr@ashroe.eu> wrote:
> >
> > Hi Anatoly & Thomas,
> >
> > The following eal experimental symbols are present in both v21.05 and v19.11 release. These symbols should be considered for promotion to stable as part of the v22 ABI in DPDK 21.11, as they have been experimental for >= 2yrs at this point.
> 
> Just an additional comment.
> Marking stable is not the only choice.
> We can also consider hiding such symbols (marking internal) if there
> is no clear usecase out of DPDK.

+1

there has to be a very strong/clear case for promotion to public.

> 
> 
> -- 
> David Marchand