From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw110231-110232 [PATCH] [2/2] net/mlx5: fix LRO configuration in drop RxQ
Date: Mon, 25 Apr 2022 05:49:07 -0400 (EDT) [thread overview]
Message-ID: <20220425094907.45F17EEAC6@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/110231
_apply patch failure_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Monday, April 25 2022 09:30:20
Applied on: CommitID:76076342ec8ef108a155938d46a88bb493fae60e
Apply patch set 110231-110232 failed:
Checking patch drivers/net/mlx5/mlx5_rxq.c...
error: while searching for:
dev->data->dev_conf.rxmode.offloads;
bool is_extmem = false;
if (mp) {
/*
* The parameters should be checked on rte_eth_dev layer.
error: patch failed: drivers/net/mlx5/mlx5_rxq.c:842
Applying patch drivers/net/mlx5/mlx5_rxq.c with 1 reject...
Rejected hunk #1.
diff a/drivers/net/mlx5/mlx5_rxq.c b/drivers/net/mlx5/mlx5_rxq.c (rejected hunks)
@@ -842,6 +842,14 @@ mlx5_rx_queue_setup(struct rte_eth_dev *dev, uint16_t idx, uint16_t desc,
dev->data->dev_conf.rxmode.offloads;
bool is_extmem = false;
+ if ((offloads & RTE_ETH_RX_OFFLOAD_TCP_LRO) &&
+ !priv->sh->dev_cap.lro_supported) {
+ DRV_LOG(ERR,
+ "Port %u queue %u LRO is configured but not supported.",
+ dev->data->port_id, idx);
+ rte_errno = EINVAL;
+ return -rte_errno;
+ }
if (mp) {
/*
* The parameters should be checked on rte_eth_dev layer.
https://lab.dpdk.org/results/dashboard/patchsets/21904/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-04-25 9:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220425094907.45F17EEAC6@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.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;
as well as URLs for NNTP newsgroup(s).