From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw60400[v2, 02/17] net/bnxt: fix traffic failure with higher mbuf size
Date: 01 Oct 2019 23:05:43 -0700 [thread overview]
Message-ID: <ee68f5$86g2nh@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/60400
_apply issues_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: 2019-10-02 05:54:08
Reply_mail: 20191002055423.99659-3-ajit.khaparde@broadcom.com
DPDK git baseline:
Repo:dpdk-next-net, CommitID: d49603df1aa275c275684ccf792cd2aab1e57e2f
Repo:dpdk, CommitID: bd253daa7717835f88bbc58b09a94d0060380396
Apply patchset failed, the failed patch is: http://dpdk.org/patch/60400
*Repo: dpdk
new_pkt_size = new_mtu + RTE_ETHER_HDR_LEN + RTE_ETHER_CRC_LEN +
VLAN_TAG_SIZE * BNXT_NUM_VLANS;
rc = bnxt_dev_info_get_op(eth_dev, &dev_info);
if (rc != 0) {
PMD_DRV_LOG(ERR, "Error during getting ethernet device info\n");
return rc;
}
if (new_mtu < RTE_ETHER_MIN_MTU || new_mtu > BNXT_MAX_MTU) {
PMD_DRV_LOG(ERR, "MTU requested must be within (%d, %d)\n",
--
#ifdef RTE_ARCH_X86
/*
* If vector-mode tx/rx is active, disallow any MTU change that would
error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:1979
error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply
Checking patch drivers/net/bnxt/bnxt_hwrm.c...
Hunk #1 succeeded at 1176 (offset -57 lines).
Hunk #2 succeeded at 1207 (offset -57 lines).
Hunk #3 succeeded at 1824 (offset -57 lines).
DPDK STV team
reply other threads:[~2019-10-02 6:05 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='ee68f5$86g2nh@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--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).