From: Stephen Hemminger <stephen@networkplumber.org>
To: Haiyue Wang <haiyue.wang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC v1 1/3] ethdev: add the Rx/Tx burst description field in queue information
Date: Mon, 12 Aug 2019 08:37:14 -0700 [thread overview]
Message-ID: <20190812083714.0cb7a7dd@hermes.lan> (raw)
In-Reply-To: <1565619305-17116-2-git-send-email-haiyue.wang@intel.com>
On Mon, 12 Aug 2019 22:15:03 +0800
Haiyue Wang <haiyue.wang@intel.com> wrote:
> Since each PMD has different Rx/Tx burst capabilities such as Vector,
> Scattered, Bulk etc, adding the Rx/Tx burst description field in queue
> information to provide apps current configuration of PMD Rx/Tx burst.
>
> This is a self-description for each PMD in its own format.
>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
I can see why it might help with diagnosing issues on VPP,
but it would have bigger impacts for other users of DPDK.
Think of a better way that doesn't break ABI.
This is not enough value to make the DPDK more unstable.
next prev parent reply other threads:[~2019-08-12 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 14:15 [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field 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 [this message]
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 ` [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field David Marchand
2019-08-12 15:38 ` 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=20190812083714.0cb7a7dd@hermes.lan \
--to=stephen@networkplumber.org \
--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).