From: David Marchand <david.marchand@redhat.com>
To: Haiyue Wang <haiyue.wang@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field
Date: Mon, 12 Aug 2019 16:27:11 +0200 [thread overview]
Message-ID: <CAJFAV8zFd5jMAtocx9K-ds6khWkTbS-K1_Qi5jQf4+W1dsOLAQ@mail.gmail.com> (raw)
In-Reply-To: <1565619305-17116-1-git-send-email-haiyue.wang@intel.com>
On Mon, Aug 12, 2019 at 4:20 PM Haiyue Wang <haiyue.wang@intel.com> wrote:
>
> Since some PMDs have multi-path for Rx/Tx, FD.io VPP will tell you in
> the Debug CLI what rx/tx function is being used:
> #show hardware-interface
>
> tx burst function: ice_xmit_pkts
> rx burst function: ice_recv_scattered_pkts
>
> But if the tx/rx is static, then 'dladdr' will return nil:
>
> tx burst function: (nil) │······················
> rx burst function: (nil) │······················
>
> For making things consistent and gracefull, we introduce an new string
> field to describe the Rx/Tx burst information. This is vendor-neutral,
> it is used to identify the Rx/Tx burst selection if the PMD has more
> than one.
>
> If a PMD supports this, then rxqinfo/txqinfo->burst_info[0] != '\0'.
The rx/tx handlers are the same for all queues of a ethdev port.
What is the added value to put this in a per queue api ?
--
David Marchand
next prev parent reply other threads:[~2019-08-12 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 14:15 Haiyue Wang
2019-08-12 14:15 ` [dpdk-dev] [RFC v1 1/3] ethdev: add the Rx/Tx burst description field in queue information Haiyue Wang
2019-08-12 15:37 ` Stephen Hemminger
2019-08-12 14:15 ` [dpdk-dev] [RFC v1 2/3] testpmd: show the Rx/Tx burst description field in queue Haiyue Wang
2019-08-12 14:15 ` [dpdk-dev] [RFC v1 3/3] net/ice: support the Rx/Tx burst description field in queue information Haiyue Wang
2019-08-12 14:27 ` David Marchand [this message]
2019-08-12 15:38 ` [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field Stephen Hemminger
2019-08-12 15:42 ` Wang, Haiyue
2019-08-12 15:54 ` Stephen Hemminger
2019-08-12 16:00 ` Wang, Haiyue
2019-08-12 17:28 ` Stephen Hemminger
2019-08-12 17:36 ` Wang, Haiyue
2019-08-12 15:39 ` Wang, Haiyue
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=CAJFAV8zFd5jMAtocx9K-ds6khWkTbS-K1_Qi5jQf4+W1dsOLAQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
/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).