From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Matan Azrad <matan@nvidia.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vdpa/mlx5: improve interrupt management
Date: Mon, 29 Mar 2021 16:09:30 +0200 [thread overview]
Message-ID: <eceddbe0-6858-ae54-93d5-c2aba5cc83af@redhat.com> (raw)
In-Reply-To: <1616058798-303292-1-git-send-email-matan@nvidia.com>
On 3/18/21 10:13 AM, Matan Azrad wrote:
> The driver should notify the guest for each traffic burst detected by CQ
> polling.
>
> The CQ polling trigger is defined by `event_mode` device argument,
> either by busy polling on all the CQs or by blocked call to HW
> completion event using DevX channel.
>
> Also, the polling event modes can move to blocked call when the
> traffic rate is low.
>
> The current blocked call uses the EAL interrupt API suffering a lot
> of overhead in the API management and serve all the drivers and
> libraries using only single thread.
>
> Use blocking FD of the DevX channel in order to do blocked call
> directly by the DevX channel FD mechanism.
>
> Signed-off-by: Matan Azrad <matan@nvidia.com>
> Acked-by: Xueming Li <xuemingl@nvidia.com>
> ---
> doc/guides/vdpadevs/mlx5.rst | 8 +-
> drivers/vdpa/mlx5/mlx5_vdpa.c | 8 +-
> drivers/vdpa/mlx5/mlx5_vdpa.h | 8 +-
> drivers/vdpa/mlx5/mlx5_vdpa_event.c | 308 +++++++++++++++---------------------
> 4 files changed, 134 insertions(+), 198 deletions(-)
>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2021-03-29 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 9:13 Matan Azrad
2021-03-29 14:09 ` Maxime Coquelin [this message]
2021-04-07 6:49 ` Xia, Chenbo
2021-04-11 9:07 ` Thomas Monjalon
2021-04-29 9:48 ` Maxime Coquelin
2021-05-02 10:47 ` Matan Azrad
2021-05-02 10:45 ` [dpdk-dev] [PATCH v2] " Matan Azrad
2021-05-03 14:27 ` Maxime Coquelin
2021-05-04 8:29 ` Maxime Coquelin
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=eceddbe0-6858-ae54-93d5-c2aba5cc83af@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.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).