DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 517] Traffic Class Assignment
Date: Mon, 27 Jul 2020 13:36:03 +0000	[thread overview]
Message-ID: <bug-517-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 517
           Summary: Traffic Class Assignment
           Product: DPDK
           Version: 18.08
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: ikaplinsky@parallelwireless.com
  Target Milestone: ---

- Unable to setup more than 1 TC
- Unable to enable TC strict priority

  testpmd> set vf tc tx min-bandwidth 0 0 (20,20,20,40)
  rte_pmd_i40e_set_vf_tc_bw_alloc(): Weight should be set for all 1 enabled
TCs.
  invalid vf_id 0 or bandwidth

  testpmd> set tx strict-link-priority 0 0x3
  rte_pmd_i40e_set_tc_strict_prio(): TC bitmap isn't the subset of enabled TCs
0x1.



  testpmd> show port dcb_tc all

      ================ DCB infos for port 0   ================
      TC NUMBER: 1

      TC :             0
      Priority :       0
      BW percent :   100%
      RXQ base :       0
      RXQ number :    64
      TXQ base :       0
      TXQ number :    64


Working on (setup description)
Host OS: Centos 7
DPDK version: 18.08.1-stable
NIC: Intel X710 Ethernet controller

ethtool info (to check driver and NIC's firmware versions)
    # ethtool -i  enp1s0f0

    driver: i40e
    version: 2.11.29
    firmware-version: 7.30 0x800083a0 1.2684.0
    expansion-rom-version:
    bus-info: 0000:01:00.0
    supports-statistics: yes
    supports-test: yes
    supports-eeprom-access: yes
    supports-register-dump: yes
    supports-priv-flags: yes

Configuration:
    # dpdk-devbind.py --status-dev=net

    Network devices using DPDK-compatible driver
    ============================================
    0000:01:00.2 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=igb_uio
unused=i40e
    0000:02:0a.0 'Ethernet Virtual Function 700 Series 154c' drv=igb_uio
unused=iavf


    Network devices using kernel driver
    ===================================
    0000:00:1f.6 'Ethernet Connection (7) I219-V 15bc' if=eno1 drv=e1000e
unused=igb_uio *Active*
    0000:01:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' if=enp1s0f0
drv=i40e unused=igb_uio
    0000:01:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' if=enp1s0f1
drv=i40e unused=igb_uio
    0000:01:00.3 'Ethernet Controller X710 for 10GbE SFP+ 1572' if=enp1s0f3
drv=i40e unused=igb_uio
    0000:02:0a.1 'Ethernet Virtual Function 700 Series 154c' if=enp2s10f1
drv=iavf unused=igb_uio
    0000:03:00.0 '82576 Gigabit Network Connection 10c9' if=enp3s0f0 drv=igb
unused=igb_uio
    0000:03:00.1 '82576 Gigabit Network Connection 10c9' if=enp3s0f1 drv=igb
unused=igb_uio
    0000:05:00.0 'Device 0001' if=enp5s0f0 drv=ixgbe unused=igb_uio
    0000:05:00.1 'Device 0001' if=enp5s0f1 drv=ixgbe unused=igb_uio

    Other Network devices
    =====================
    <none>

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

                 reply	other threads:[~2020-07-27 13:36 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=bug-517-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).