From: Asaf Penso <asafp@mellanox.com>
To: dev@dpdk.org
Cc: Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [PATCH 0/4] vdpa/mlx5: support direct notification
Date: Tue, 24 Mar 2020 14:24:33 +0000 [thread overview]
Message-ID: <1585059877-2369-1-git-send-email-asafp@mellanox.com> (raw)
In order to save CPU usage in host and even make it 0 when guest work with poll mode,
add support for direct doorbell ringing.
Now, when the feature is supported in QEMU, the guest doorbell address is mapped directly to the HW doorbell space and the host SW relay is not used.
Matan Azrad (4):
vdpa/mlx5: move virtual doorbell alloc to probe
vdpa/mlx5: support direct HW notifications
vdpa/mlx5: validate notifier configuration
vdpa/mlx5: add log prints
drivers/vdpa/mlx5/mlx5_vdpa.c | 90 +++++++++++++++++++++++++++++++------
drivers/vdpa/mlx5/mlx5_vdpa.h | 1 +
drivers/vdpa/mlx5/mlx5_vdpa_steer.c | 2 +
drivers/vdpa/mlx5/mlx5_vdpa_virtq.c | 39 ++++++++--------
4 files changed, 100 insertions(+), 32 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-03-24 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 14:24 Asaf Penso [this message]
2020-03-24 14:24 ` [dpdk-dev] [PATCH 1/4] vdpa/mlx5: move virtual doorbell alloc to probe Asaf Penso
2020-04-15 9:44 ` Maxime Coquelin
2020-03-24 14:24 ` [dpdk-dev] [PATCH 2/4] vdpa/mlx5: support direct HW notifications Asaf Penso
2020-04-15 9:47 ` Maxime Coquelin
2020-04-17 11:54 ` Maxime Coquelin
2020-04-26 7:06 ` Matan Azrad
2020-04-27 7:45 ` Maxime Coquelin
2020-03-24 14:24 ` [dpdk-dev] [PATCH 3/4] vdpa/mlx5: validate notifier configuration Asaf Penso
2020-04-15 9:54 ` Maxime Coquelin
2020-03-24 14:24 ` [dpdk-dev] [PATCH 4/4] vdpa/mlx5: add log prints Asaf Penso
2020-04-17 11:54 ` Maxime Coquelin
2020-04-17 17:14 ` [dpdk-dev] [PATCH 0/4] vdpa/mlx5: support direct notification 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=1585059877-2369-1-git-send-email-asafp@mellanox.com \
--to=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=shahafs@mellanox.com \
--cc=viacheslavo@mellanox.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).