All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1098] net/iavf: check_rx_vec_allow() result is ignored
Date: Tue, 11 Oct 2022 13:25:45 +0000	[thread overview]
Message-ID: <bug-1098-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1098
           Summary: net/iavf: check_rx_vec_allow() result is ignored
           Product: DPDK
           Version: 22.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: maxime.coquelin@redhat.com
  Target Milestone: ---

In IAVF driver, check_rx_vec_allow() ensure some conditions are met to
authorize vector path usage for a given Rxq.

Its return is assigned to Rxq's (struct iavf_adapter *)->rx_vec_allowed in
iavf_dev_rx_queue_setup(), but (struct iavf_adapter *)->rx_vec_allowed is never
used afterwards.

Either conditions checked in check_rx_vec_allow() are useless and so it should
be removed, or DP selection should take .rx_vec_allowed value into account.

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

                 reply	other threads:[~2022-10-11 13:25 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-1098-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.