From: Stephen Hemminger <stephen@networkplumber.org>
To: Yasin CANER <yasinncaner@gmail.com>
Cc: users@dpdk.org
Subject: Re: rte_ip_frag_table_del_expired_entries gives warning about deprecation - 22.11.5
Date: Thu, 14 Nov 2024 08:20:47 -0800 [thread overview]
Message-ID: <20241114082047.69be9c69@hermes.local> (raw)
In-Reply-To: <CAP5epcNyXraApMB1bLtT3V=qMKN6WkSGhA780acA-Ya=+H+=og@mail.gmail.com>
On Thu, 14 Nov 2024 13:24:32 +0300
Yasin CANER <yasinncaner@gmail.com> wrote:
> Hello Team,
> I am currently using DPDK version 22.11.5 and have encountered a
> deprecation warning for the rte_ip_frag_table_del_expired_entries function.
> Could you please advise on the recommended method for deleting expired
> entries in the fragmentation table?
> Additionally, if it is still safe to use this function, is it acceptable to
> call it every 5 seconds?
> Thank you for your assistance.
>
>
> https://doc.dpdk.org/guides/prog_guide/ip_fragment_reassembly_lib.html
>
> https://doc.dpdk.org/api/rte__ip__frag_8h.html#acb22ee9956900b57d4d8ac75c70abe4d
>
> Best regards.
>
> ___
>
> Yasin CANER
See release notes for 21.11 for when it changed.
https://doc.dpdk.org/guides-22.11/rel_notes/release_21_11.html
ip_frag: All macros updated to have RTE_IP_FRAG_ prefix. Obsolete macros are kept for compatibility. DPDK components updated to use new names. Experimental function rte_frag_table_del_expired_entries() was renamed to rte_ip_frag_table_del_expired_entries() to comply with other public API naming convention.
prev parent reply other threads:[~2024-11-14 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 10:24 Yasin CANER
2024-11-14 16:20 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241114082047.69be9c69@hermes.local \
--to=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=yasinncaner@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).