From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw114719 [PATCH] [v2] net/tap: Allow jumbo frames
Date: Mon, 8 Aug 2022 07:40:59 -0400 (EDT) [thread overview]
Message-ID: <20220808114059.62634B296@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/114719
_apply patch failure_
Submitter: Francesco Mancino <francesco.mancino@tutus.se>
Date: Monday, August 08 2022 11:32:09
Applied on: CommitID:72206323a5dd3182b13f61b25a64abdddfee595c
Apply patch set 114719 failed:
Checking patch drivers/net/tap/rte_eth_tap.c...
error: while searching for:
dev_info->if_index = internals->if_index;
dev_info->max_mac_addrs = 1;
dev_info->max_rx_pktlen = (uint32_t)RTE_ETHER_MAX_VLAN_FRAME_LEN;
dev_info->max_rx_queues = RTE_PMD_TAP_MAX_QUEUES;
dev_info->max_tx_queues = RTE_PMD_TAP_MAX_QUEUES;
dev_info->min_rx_bufsize = 0;
error: patch failed: drivers/net/tap/rte_eth_tap.c:1066
Applying patch drivers/net/tap/rte_eth_tap.c with 1 reject...
Rejected hunk #1.
diff a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c (rejected hunks)
@@ -1066,7 +1066,7 @@ tap_dev_info(struct rte_eth_dev *dev, struct rte_eth_dev_info *dev_info)
dev_info->if_index = internals->if_index;
dev_info->max_mac_addrs = 1;
- dev_info->max_rx_pktlen = (uint32_t)RTE_ETHER_MAX_VLAN_FRAME_LEN;
+ dev_info->max_rx_pktlen = (uint32_t)RTE_ETHER_MAX_JUMBO_FRAME_LEN;
dev_info->max_rx_queues = RTE_PMD_TAP_MAX_QUEUES;
dev_info->max_tx_queues = RTE_PMD_TAP_MAX_QUEUES;
dev_info->min_rx_bufsize = 0;
https://lab.dpdk.org/results/dashboard/patchsets/23164/
UNH-IOL DPDK Community Lab
next reply other threads:[~2022-08-08 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 11:40 dpdklab [this message]
[not found] <685052b7-2a27-32e6-9671-b1a28f6ba604@tutus.se>
2022-08-08 11:32 ` |WARNING| pw114719 [PATCH v2] " checkpatch
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=20220808114059.62634B296@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).