From: "Kadam, Pallavi" <pallavi.kadam@intel.com>
To: Robin Zhang <robinx.zhang@intel.com>, <dev@dpdk.org>
Cc: <jingjing.wu@intel.com>, <beilei.xing@intel.com>,
<qi.z.zhang@intel.com>, <junfeng.guo@intel.com>,
<stevex.yang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/iavf: enable interrupt polling
Date: Tue, 14 Sep 2021 16:06:55 -0700 [thread overview]
Message-ID: <101076ef-f5e5-68fa-c93a-2eac6e65fa51@intel.com> (raw)
In-Reply-To: <20210825083435.207234-1-robinx.zhang@intel.com>
On 8/25/2021 1:34 AM, Robin Zhang wrote:
> For VF hosted by Intel 700 series NICs, internal rx interrupt and adminq
> interrupt share the same source, that cause a lot cpu cycles be wasted on
> interrupt handler on rx path.
>
> The patch disable pci interrupt and remove the interrupt handler, replace
> it with a low frequency(50ms) interrupt polling daemon which is
> implemtented by registering an alarm callback periodly.
>
> The virtual channel capability bit VIRTCHNL_VF_OFFLOAD_WB_ON_ITR can be
> used to negotiate if iavf PMD needs to enable background alarm or not, so
> ideally this change will not impact the case hosted by Intel 800 series
> NICS.
>
> This patch implements the same logic with an early i40e commit:
> commit 864a800d706d ("net/i40e: remove VF interrupt handler")
>
> Signed-off-by: Robin Zhang <robinx.zhang@intel.com>
>
> v2:
> - only enable interrupt polling for VF of i40e devices.
>
> ---
Acked-by: Pallavi Kadam <pallavi.kadam@intel.com>
next prev parent reply other threads:[~2021-09-14 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 7:46 [dpdk-dev] [PATCH] net/iavf: remove interrupt handler Robin Zhang
2021-08-10 7:10 ` Zhang, Qi Z
2021-08-12 7:41 ` Wu, Jingjing
2021-08-25 8:34 ` [dpdk-dev] [PATCH v2] net/iavf: enable interrupt polling Robin Zhang
2021-09-14 23:06 ` Kadam, Pallavi [this message]
2021-09-22 7:26 ` 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=101076ef-f5e5-68fa-c93a-2eac6e65fa51@intel.com \
--to=pallavi.kadam@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=robinx.zhang@intel.com \
--cc=stevex.yang@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).