DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] [Bug 554] shutdown_api/test_change_thresholds: Port config all rxpt, rxht, rxwt are invalid
@ 2020-10-14 10:02 bugzilla
  2021-01-29  7:56 ` bugzilla
  0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2020-10-14 10:02 UTC (permalink / raw)
  To: dev

https://bugs.dpdk.org/show_bug.cgi?id=554

            Bug ID: 554
           Summary: shutdown_api/test_change_thresholds: Port config all
                    rxpt, rxht, rxwt are invalid
           Product: DPDK
           Version: 20.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: linglix.chen@intel.com
  Target Milestone: ---

Created attachment 124
  --> https://bugs.dpdk.org/attachment.cgi?id=124&action=edit
shutdown_api/test_change_thresholds-FAILED-log

Environment:
•DPDK version: 20.11.0-rc0  commit 700ded7aa15f5ecc5b68d12fcb6fd3bfe06e599d
•OS: CentOS8.2/4.18.0-193.6.3.el8_2.x86_64
•Compiler: gcc  8.3.1
•Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
•NIC hardware: 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
•NIC firmware: 0x000161bf
•NIC driver version: 5.1.0-k-rh8.2.0


Steps to reproduce:
1. Bind 2 PFs to vfio-pci. 
#dpdk-devbind.py --force --bind=vfio-pci 0000:81:00.0 0000:81:00.1 
2. Launch testpmd. 
#x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1,2 -n 4 -w 0000:81:00.0 -w
0000:81:00.1 --file-prefix=dpdk_10376_20201015182508 -- -i --portmask=0x1
--port-topology=loop 
testpmd> set promisc all off 
testpmd> port stop all 
testpmd> port config all rxpt 64
testpmd> port config all rxht 64
testpmd> port config all rxwt 64 
testpmd> port start all 
testpmd> show config rxtx

Actual Result:
port 0: RX queue number: 1 Tx queue number: 1
    Rx offloads=0x0 Tx offloads=0x0
    RX queue: 0
      RX desc=256 - RX free threshold=32
      RX threshold registers: pthresh=0 hthresh=0  wthresh=0
      RX Offloads=0x0
    TX queue: 0
      TX desc=256 - TX free threshold=32
      TX threshold registers: pthresh=64 hthresh=64  wthresh=0
      TX offloads=0x0 - TX RS bit threshold=32
  port 1: RX queue number: 1 Tx queue number: 1
    Rx offloads=0x0 Tx offloads=0x0
    RX queue: 0
      RX desc=256 - RX free threshold=32
      RX threshold registers: pthresh=0 hthresh=0  wthresh=0
      RX Offloads=0x0
    TX queue: 0
      TX desc=256 - TX free threshold=32
      TX threshold registers: pthresh=64 hthresh=64  wthresh=0
      TX offloads=0x0 - TX RS bit threshold=32


Expected Result:
port 0: RX queue number: 1 Tx queue number: 1
    Rx offloads=0x0 Tx offloads=0x0
    RX queue: 0
      RX desc=256 - RX free threshold=32
      RX threshold registers: pthresh=64 hthresh=64  wthresh=64
      RX Offloads=0x0
    TX queue: 0
      TX desc=256 - TX free threshold=32
      TX threshold registers: pthresh=64 hthresh=64  wthresh=0
      TX offloads=0x0 - TX RS bit threshold=32
  port 1: RX queue number: 1 Tx queue number: 1
    Rx offloads=0x0 Tx offloads=0x0
    RX queue: 0
      RX desc=256 - RX free threshold=32
      RX threshold registers: pthresh=64 hthresh=64  wthresh=64
      RX Offloads=0x0
    TX queue: 0
      TX desc=256 - TX free threshold=32
      TX threshold registers: pthresh=64 hthresh=64  wthresh=0     
      TX offloads=0x0 - TX RS bit threshold=32 


Regression:
Is this issue a regression: Y
First bad commit:
commit 700ded7aa15f5ecc5b68d12fcb6fd3bfe06e599d (HEAD -> master)
Author: Huisong Li <lihuisong@huawei.com>
Date:   Fri Sep 25 20:47:19 2020 +0800

    app/testpmd: fix displaying Rx/Tx queues information

    Currently, the information of Rx/Tx queues from PMD driver is not
    displayed exactly in the rxtx_config_display function. Because
    "ports[pid].rx_conf" and "ports[pid].tx_conf" maintained in testpmd
    application may be not the value actually used by PMD driver. For
    instance, user does not set a field, but PMD driver has to use the
    default value.

    This patch fixes rxtx_config_display so that the information of Rx/Tx
    queues can be really displayed for the PMD driver that implement
    .rxq_info_get and .txq_info_get ops callback function.

    Fixes: 75c530c1bd53 ("app/testpmd: fix port configuration print")
    Fixes: d44f8a485f5d ("app/testpmd: enable per queue configure")
    Cc: stable@dpdk.org

    Signed-off-by: Huisong Li <lihuisong@huawei.com>
    Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com>
    Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [dpdk-dev] [Bug 554] shutdown_api/test_change_thresholds: Port config all rxpt, rxht, rxwt are invalid
  2020-10-14 10:02 [dpdk-dev] [Bug 554] shutdown_api/test_change_thresholds: Port config all rxpt, rxht, rxwt are invalid bugzilla
@ 2021-01-29  7:56 ` bugzilla
  0 siblings, 0 replies; 2+ messages in thread
From: bugzilla @ 2021-01-29  7:56 UTC (permalink / raw)
  To: dev

https://bugs.dpdk.org/show_bug.cgi?id=554

Zhang, RobinX (robinx.zhang@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
                 CC|                            |robinx.zhang@intel.com
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from Zhang, RobinX (robinx.zhang@intel.com) ---
82599 NIC not support this feature on rx.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-01-29  7:56 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-14 10:02 [dpdk-dev] [Bug 554] shutdown_api/test_change_thresholds: Port config all rxpt, rxht, rxwt are invalid bugzilla
2021-01-29  7:56 ` bugzilla

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).