From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, mdr@ashroe.eu
Subject: Re: [dpdk-dev] [PATCH v4 2/2] ip_frag: add namespace
Date: Mon, 08 Nov 2021 22:36:05 +0100 [thread overview]
Message-ID: <40912187.gXRZthq1ag@thomas> (raw)
In-Reply-To: <20211108135555.24164-3-konstantin.ananyev@intel.com>
08/11/2021 14:55, Konstantin Ananyev:
> Update public macros to have RTE_IP_FRAG_ prefix.
> Remove obsolete macro.
> Update DPDK components to use new names.
I think you should keep old names for compatibility during some time.
We should rename the function rte_frag_table_del_expired_entries
to start with rte_ip_frag_ like others.
> --- a/lib/ip_frag/rte_ip_frag.h
> +++ b/lib/ip_frag/rte_ip_frag.h
> @@ -27,22 +27,19 @@ extern "C" {
>
> struct rte_mbuf;
>
> -#define IP_FRAG_DEATH_ROW_LEN 32 /**< death row size (in packets) */
> +#define RTE_IP_FRAG_DEATH_ROW_LEN 32 /**< death row size (in packets) */
>
> /* death row size in mbufs */
> -#define IP_FRAG_DEATH_ROW_MBUF_LEN \
> - (IP_FRAG_DEATH_ROW_LEN * (RTE_LIBRTE_IP_FRAG_MAX_FRAG + 1))
> +#define RTE_IP_FRAG_DEATH_ROW_MBUF_LEN \
> + (RTE_IP_FRAG_DEATH_ROW_LEN * (RTE_LIBRTE_IP_FRAG_MAX_FRAG + 1))
>
> /** mbuf death row (packets to be freed) */
> struct rte_ip_frag_death_row {
> uint32_t cnt; /**< number of mbufs currently on death row */
> - struct rte_mbuf *row[IP_FRAG_DEATH_ROW_MBUF_LEN];
> + struct rte_mbuf *row[RTE_IP_FRAG_DEATH_ROW_MBUF_LEN];
> /**< mbufs to be freed */
> };
>
> -/* struct ipv6_extension_fragment moved to librte_net/rte_ip.h and renamed. */
> -#define ipv6_extension_fragment rte_ipv6_fragment_ext
> -
> /**
> * Create a new IP fragmentation table.
> *
> @@ -128,7 +125,7 @@ rte_ipv6_fragment_packet(struct rte_mbuf *pkt_in,
> struct rte_mbuf *rte_ipv6_frag_reassemble_packet(struct rte_ip_frag_tbl *tbl,
> struct rte_ip_frag_death_row *dr,
> struct rte_mbuf *mb, uint64_t tms, struct rte_ipv6_hdr *ip_hdr,
> - struct ipv6_extension_fragment *frag_hdr);
> + struct rte_ipv6_fragment_ext *frag_hdr);
>
> /**
> * Return a pointer to the packet's fragment header, if found.
> @@ -141,11 +138,11 @@ struct rte_mbuf *rte_ipv6_frag_reassemble_packet(struct rte_ip_frag_tbl *tbl,
> * Pointer to the IPv6 fragment extension header, or NULL if it's not
> * present.
> */
> -static inline struct ipv6_extension_fragment *
> +static inline struct rte_ipv6_fragment_ext *
> rte_ipv6_frag_get_ipv6_fragment_header(struct rte_ipv6_hdr *hdr)
> {
> if (hdr->proto == IPPROTO_FRAGMENT) {
> - return (struct ipv6_extension_fragment *) ++hdr;
> + return (struct rte_ipv6_fragment_ext *) ++hdr;
> }
> else
> return NULL;
next prev parent reply other threads:[~2021-11-08 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 12:24 [dpdk-dev] [PATCH] ip_frag: hide internal structures Konstantin Ananyev
2021-11-01 12:49 ` [dpdk-dev] [PATCH v2] " Konstantin Ananyev
2021-11-04 18:30 ` Thomas Monjalon
2021-11-08 11:51 ` [dpdk-dev] [PATCH v3] " Konstantin Ananyev
2021-11-08 13:55 ` [dpdk-dev] [PATCH v4 0/2] ip_frag cleanup patches Konstantin Ananyev
2021-11-08 13:55 ` [dpdk-dev] [PATCH v4 1/2] ip_frag: hide internal structures Konstantin Ananyev
2021-11-08 21:39 ` Thomas Monjalon
2021-11-08 13:55 ` [dpdk-dev] [PATCH v4 2/2] ip_frag: add namespace Konstantin Ananyev
2021-11-08 21:36 ` Thomas Monjalon [this message]
2021-11-09 12:32 ` [dpdk-dev] [PATCH v5] " Konstantin Ananyev
2021-11-17 9:25 ` Thomas Monjalon
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=40912187.gXRZthq1ag@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=mdr@ashroe.eu \
/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).