From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Kamil Vojanec <vojanec@cesnet.cz>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Trevor Tao <taozj888@163.com>
Subject: Re: [PATCH] examples/l3fwd: fix conf propagation to RX queues
Date: Thu, 07 Mar 2024 09:47:38 +0100 [thread overview]
Message-ID: <3211208.NnENhoQgcM@thomas> (raw)
In-Reply-To: <20240216120207.126025-1-vojanec@cesnet.cz>
Review please?
16/02/2024 13:02, Kamil Vojanec:
> When configuring RX queues, the default port configuration was used,
> even though it was modified before. This results in the
> 'relax-rx-offload' not being respected for RX queues.
> This commit uses 'rte_eth_dev_conf_get()' to obtain the device
> configuration structure instead.
>
> Fixes: 4b01cabfb0 ("examples/l3fwd: add option to relax Rx offload")
> Signed-off-by: Kamil Vojanec <vojanec@cesnet.cz>
next prev parent reply other threads:[~2024-03-07 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 12:02 Kamil Vojanec
2024-03-07 8:47 ` Thomas Monjalon [this message]
2024-03-07 10:14 ` Konstantin Ananyev
2024-03-07 15:03 ` Thomas Monjalon
2024-03-07 14:07 ` Kevin Traynor
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=3211208.NnENhoQgcM@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=taozj888@163.com \
--cc=vojanec@cesnet.cz \
/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).