From: Bruce Richardson <bruce.richardson@intel.com>
To: Euan Bourke <euan.bourke@intel.com>
Cc: <dev@dpdk.org>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
"Radu Nicolau" <radu.nicolau@intel.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: Re: [PATCH v3 2/2] ip_frag: updated name for IP frag max frag define
Date: Fri, 22 Dec 2023 09:08:59 +0000 [thread overview]
Message-ID: <ZYVSKz9gqyXkgBEA@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20231221174140.3369894-2-euan.bourke@intel.com>
On Thu, Dec 21, 2023 at 05:41:40PM +0000, Euan Bourke wrote:
> Removed LIBRTE from name as its an old prefix.
>
> Signed-off-by: Euan Bourke <euan.bourke@intel.com>
> ---
> app/test/test_reassembly_perf.c | 2 +-
> config/rte_config.h | 2 +-
> doc/guides/prog_guide/ip_fragment_reassembly_lib.rst | 8 ++++----
> doc/guides/sample_app_ug/ip_reassembly.rst | 4 ++--
> examples/ip_fragmentation/main.c | 2 +-
> examples/ip_reassembly/main.c | 2 +-
> examples/ipsec-secgw/ipsec_worker.h | 2 +-
> lib/ip_frag/ip_reassembly.h | 2 +-
> lib/ip_frag/rte_ip_frag.h | 2 +-
> 9 files changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/app/test/test_reassembly_perf.c b/app/test/test_reassembly_perf.c
> index 3912179022..805ae2fe9d 100644
> --- a/app/test/test_reassembly_perf.c
> +++ b/app/test/test_reassembly_perf.c
> @@ -20,7 +20,7 @@
> #define MAX_FLOWS (1024 * 32)
> #define MAX_BKTS MAX_FLOWS
> #define MAX_ENTRIES_PER_BKT 16
> -#define MAX_FRAGMENTS RTE_LIBRTE_IP_FRAG_MAX_FRAG
> +#define MAX_FRAGMENTS RTE_IP_FRAG_MAX_FRAG
> #define MIN_FRAGMENTS 2
> #define MAX_PKTS (MAX_FLOWS * MAX_FRAGMENTS)
>
> diff --git a/config/rte_config.h b/config/rte_config.h
> index da265d7dd2..e2fa2a58fa 100644
> --- a/config/rte_config.h
> +++ b/config/rte_config.h
> @@ -85,7 +85,7 @@
> #define RTE_RAWDEV_MAX_DEVS 64
>
> /* ip_fragmentation defines */
> -#define RTE_LIBRTE_IP_FRAG_MAX_FRAG 8
> +#define RTE_IP_FRAG_MAX_FRAG 8
> // RTE_LIBRTE_IP_FRAG_TBL_STAT is not set
>
> /* rte_power defines */
> diff --git a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst
> index f3ed90d700..2d422309bb 100644
> --- a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst
> +++ b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst
> @@ -43,12 +43,12 @@ Note that all update/lookup operations on Fragment Table are not thread safe.
> So if different execution contexts (threads/processes) will access the same table simultaneously,
> then some external syncing mechanism have to be provided.
>
> -Each table entry can hold information about packets of up to ``RTE_LIBRTE_IP_FRAG_MAX_FRAG`` fragments,
> -where ``RTE_LIBRTE_IP_FRAG_MAX_FRAG`` defaults to:
> +Each table entry can hold information about packets of up to ``RTE_IP_FRAG_MAX_FRAG`` fragments,
> +where ``RTE_IP_FRAG_MAX_FRAG`` defaults to:
>
> .. literalinclude:: ../../../config/rte_config.h
> :language: c
> - :start-at: #define RTE_LIBRTE_IP_FRAG_MAX_FRAG
> + :start-at: #define RTE_IP_FRAG_MAX_FRAG
> :lines: 1
>
> Code example, that demonstrates creation of a new Fragment table:
> @@ -69,7 +69,7 @@ Also, entries that resides in the table longer then <max_cycles> are considered
> and could be removed/replaced by the new ones.
>
> Note that reassembly demands a lot of mbuf's to be allocated.
> -At any given time up to (2 \* bucket_entries \* RTE_LIBRTE_IP_FRAG_MAX \* <maximum number of mbufs per packet>)
> +At any given time up to (2 \* bucket_entries \* RTE_IP_FRAG_MAX \* <maximum number of mbufs per packet>)
Should be RTE_IP_FRAG_MAX_FRAG. You should check all other replacements to
ensure the correct define name is being used. I see a couple of other
occurances in this patch where the name is wrong.
> can be stored inside Fragment Table waiting for remaining fragments.
>
<snip for brevity>
next prev parent reply other threads:[~2023-12-22 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <https://inbox.dpdk.org/dev/20231219151754.3285058-1-euan.bourke@intel.com/>
2023-12-21 11:32 ` [PATCH v2 1/2] doc: updated incorrect value for IP frag max fragments Euan Bourke
2023-12-21 11:32 ` [PATCH v2 2/2] ip_frag: updated name for IP frag define Euan Bourke
2023-12-21 11:39 ` [PATCH v2 1/2] doc: updated incorrect value for IP frag max fragments David Marchand
2023-12-21 11:41 ` Thomas Monjalon
2023-12-21 13:46 ` Bourke, Euan
2023-12-21 17:41 ` [PATCH v3 " Euan Bourke
2023-12-21 17:41 ` [PATCH v3 2/2] ip_frag: updated name for IP frag max frag define Euan Bourke
2023-12-22 9:08 ` Bruce Richardson [this message]
2024-01-08 11:36 ` [PATCH v4 1/2] doc: updated incorrect value for IP frag max fragments Euan Bourke
2024-01-08 11:36 ` [PATCH v4 2/2] ip_frag: updated name for IP frag define Euan Bourke
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=ZYVSKz9gqyXkgBEA@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=euan.bourke@intel.com \
--cc=gakhil@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=radu.nicolau@intel.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).