DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1102] i40e: enabling Rx/Tx queue deferred start has no effect
Date: Wed, 12 Oct 2022 06:38:00 +0000	[thread overview]
Message-ID: <bug-1102-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1102
           Summary: i40e: enabling Rx/Tx queue deferred start has no
                    effect
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: ivan.malov@oktetlabs.ru
  Target Milestone: ---

Created attachment 223
  --> https://bugs.dpdk.org/attachment.cgi?id=223&action=edit
probable fix

As part of the ongoing efforts [1] to bring up sophisticated DPDK PMD testing,
it was found that i40e had a bug in deferred queue start feature.

Test logs [2] and [3] suggest that the problem manifests itself both in Rx and
Tx cases. The target queue marked for deferred start proves active at the point
where the test has not yet asked to enable it.

Our takeaway from studying i40e code is that the driver does not check whether
a  queue has been marked for deferred start when enabling all queues on port
start. Please find the probable fix attached.

[1] http://mails.dpdk.org/archives/dev/2022-October/251663.html
[2] https://ts-factory.io/bublik/v2/log/100333?focusId=101010&mode=treeAndlog
[3] https://ts-factory.io/bublik/v2/log/100333?focusId=101022&mode=treeAndlog

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

                 reply	other threads:[~2022-10-12  6:38 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-1102-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).