From: Stephen Hemminger <stephen@networkplumber.org>
To: Mingjin Ye <mingjinx.ye@intel.com>
Cc: dev@dpdk.org, qiming.yang@intel.com, yidingx.zhou@intel.com,
Jingjing Wu <jingjing.wu@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: Re: [POC v2] net/iavf: support no data path polling mode
Date: Thu, 20 Jul 2023 08:45:03 -0700 [thread overview]
Message-ID: <20230720084503.5f27b0e8@hermes.local> (raw)
In-Reply-To: <20230720100815.440778-1-mingjinx.ye@intel.com>
On Thu, 20 Jul 2023 10:08:14 +0000
Mingjin Ye <mingjinx.ye@intel.com> wrote:
> Introduces a devargs "no-poll-on-link-down" in iavf PMD. When this
> flag is set, the PMD switches to no-poll mode when the link state is
> down (rx/tx burst returns to 0 immediately). When the link state
> returns to normal, PMD switches to normal rx/tx burst state.
>
> Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
There is not enough explanation of this.
Why is this necessary?
Why is it unique to the iavf device and not true of other devices?
Where is the documentation?
next prev parent reply other threads:[~2023-07-20 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 6:16 [PATCH] net/ice: CVL support double vlan Mingjin Ye
2023-05-06 10:04 ` [PATCH v2] net/ice: " Mingjin Ye
2023-05-26 10:16 ` Xu, Ke1
2023-05-26 11:10 ` Zhang, Qi Z
2023-07-17 9:36 ` [POC] net/iavf: support no data path polling mode Mingjin Ye
2023-07-20 10:08 ` [POC v2] " Mingjin Ye
2023-07-20 15:45 ` Stephen Hemminger [this message]
2023-07-21 9:57 ` [POC v3] " Mingjin Ye
2023-08-11 6:27 ` [PATCH] " Mingjin Ye
2023-09-26 7:56 ` [PATCH v2] " Mingjin Ye
2023-10-13 1:27 ` [PATCH v3] " Mingjin Ye
2023-10-17 1:44 ` [PATCH v4] " Mingjin Ye
2023-10-17 2:19 ` Mingjin Ye
2023-10-19 9:04 ` [PATCH v5] net/iavf: data paths support no-polling mode Mingjin Ye
2023-10-20 0:39 ` Zhang, Qi Z
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=20230720084503.5f27b0e8@hermes.local \
--to=stephen@networkplumber.org \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mingjinx.ye@intel.com \
--cc=qiming.yang@intel.com \
--cc=yidingx.zhou@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).