All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1139] expose selection of PMD fast-path functions before dev_start (rte_eth_dev_start)
Date: Fri, 02 Dec 2022 03:50:25 +0000	[thread overview]
Message-ID: <bug-1139-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1139
           Summary: expose selection of PMD fast-path functions before
                    dev_start (rte_eth_dev_start)
           Product: DPDK
           Version: 22.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: wdy_s@foxmail.com
  Target Milestone: ---

Created attachment 235
  --> https://bugs.dpdk.org/attachment.cgi?id=235&action=edit
diff

1. startup counsumer thread(main_loop) call rte_eth_rx_burst.
but the real rx_burst is dummy_eth_rx_burst
2. call rte_eth_dev_start: will startup dev and expose selection of PMD
fast-path functions 
3. get xstats by name("rx_missed_errors"), maybe see misserr greater than 0

my solution:
expose selection of PMD fast-path functions before dev_start
(rte_eth_dev_start)

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

                 reply	other threads:[~2022-12-02  3:50 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-1139-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.