DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Andrei-Niculae Petre <p31andrei@gmail.com>
Cc: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
	Sean Morrissey <sean.morrissey@intel.com>,
	stable@dpdk.org
Subject: Re: [PATCH v3] examples/l3fwd: fix compilation when DP debug on
Date: Thu, 12 Nov 2026 22:23:54 +0100	[thread overview]
Message-ID: <h2Pe81DMT4Wbag_ICm5Ztg@monjalon.net> (raw)
In-Reply-To: <20261107221707.20990-1-p31andrei@gmail.com>

07/11/2026 23:17, Andrei-Niculae Petre:
> Update l3fwd example app to fix compilation when building dpdk with
> RTE_LOG_DP_LEVEL=RTE_LOG_DEBUG in config/rte_config.h .
> Move l3fwd_acl.h include above all #ifdef L3FWDACL_DEBUG checks,
> as previously one ifdef would evaluate to false all the time (as
> header include was added too late).
> 
> Adapt maintainers line from previous examples/l3fwd-acl (removed in
> 6de0ea50e9b9) to examples/l3fwd/l3fwd_acl* after l3fwd-acl app
> unification into l3fwd. In 6de0ea50e9b9, a line with maintainer
> expertise was removed.

It is not related to the compilation fix, but OK to add this line.

> 
> Own testing of the l3fwd example:
> 1. It now compiles with "#define RTE_LOG_DP_LEVEL RTE_LOG_DEBUG" in
>    config/rte_config.h. See Bugzilla ID 1318 comments for full error
>    seen before this patch.
> 2. I ran the l3fwd app with IPv4/IPv6 ACL rules to see the prints (when
>    RTE_LOG_DP_LEVEL RTE_LOG_DEBUG is set) in the application around ACL
>    work as expected. See extract below (I added \ to format to 72chars):
> 
> // dump_acl4_rule extract:
> Packet Src:192.168.1.100 Dst:192.168.1.101 Src port:2048,Dst port:1846 \
> hit ACL 1 - 192.168.1.100/24 0.0.0.0/0 0 : 65535 0 : 65535 0x0/0x0 \
> 0xffffffff-0x1ffffffe-0xf0000001
> 
> // dump_acl6_rule extract:
> Packet Src2001:db8:1::100
> Dst2001:db8:1::101
> Src port:32768,Dst port:21005 hit ACL 0 - \
> 2001:0db8:0001:0000:0000:0000:0000:0000/64 \
> 0000:0000:0000:0000:0000:0000:0000:0000/0 0 : 65535 0 : 65535 \
> 0x0/0x0 0xffffffff-0x1fffffff-0xf0000000

These testing results are unrelated. Dropped.

> Bugzilla ID: 1318
> Fixes: 6de0ea50e9b9 ("examples/l3fwd: merge l3fwd-acl example")
> Cc: stable@dpdk.org
> Cc: sean.morrissey@intel.com
> 
> Signed-off-by: Andrei-Niculae Petre <p31andrei@gmail.com>

Applied, thanks.



      reply	other threads:[~2026-11-12 21:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  2:51 [PATCH] examples/l3fwd: fix compilation when DP debug on Andrei-Niculae Petre
2026-07-31 13:37 ` [PATCH v2] " Andrei-Niculae Petre
2026-09-08 18:10   ` Stephen Hemminger
2026-09-08 19:16     ` Andrei Petre
2026-11-07 22:17 ` [PATCH v3] " Andrei-Niculae Petre
2026-11-12 21:23   ` Thomas Monjalon [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=h2Pe81DMT4Wbag_ICm5Ztg@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=p31andrei@gmail.com \
    --cc=sean.morrissey@intel.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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