From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(88897) update Intel roadmap for 21.05
Date: 10 Mar 2021 11:01:23 -0800 [thread overview]
Message-ID: <d0e636$hv8hdj@fmsmga005-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/88897
_apply issues_
Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: 2021-03-10 18:39:57
Reply_mail: 20210310183957.2611798-1-ferruh.yigit@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: 1e28e842e08428ff5716fbe909bf5acd0365aaf6
* Repo: dpdk
net/hns3: fix imprecise statistics
Currently, the hns3 statistics may be inaccurate due to the
following two problems:
1. Queue-level statistics are read from the firmware, and only one Rx or
Tx can be read at a time. This results in a large time interval
--
2. The current statistics are read by type. The HW statistics are read
first, and then the software statistics are read. Due to preceding
reasons, HW reading may be time-consuming, which cause a
synchronization problem between SW and HW statistics of the same
queue.
In this patch, queue-level statistics are directly read from the bar
--
Starting new HTTP connection (1): proxy-shz.intel.com
error: content/roadmap/_index.md: does not exist in index
Applying: update Intel roadmap for 21.05
Patch failed at 0001 update Intel roadmap for 21.05
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2021-03-10 19:01 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='d0e636$hv8hdj@fmsmga005-auth.fm.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).