qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yuval Shaia <yuval.shaia.ml@gmail.com>
To: qemu-devel@nongnu.org, yuval.shaia.ml@gmail.com,
	marcel.apfelbaum@gmail.com
Subject: [PATCH v1 0/2] hw/rdma: Last step in eliminating data-path processing
Date: Fri, 20 Mar 2020 16:34:27 +0200	[thread overview]
Message-ID: <20200320143429.9490-1-yuval.shaia.ml@gmail.com> (raw)

With emulated device we have the luxury of doing things in data-path.
Considering a future virtio-rdma device we no longer have this luxury. The
driver will directly post WQEs to HW queues, bypassing the device emulator
in qemu. These WQEs will consist of addresses known to the device (even if
it is guest addresses) and ID of an HW memory region (mr).

Commit 68b89aee71 ("Utilize ibv_reg_mr_iova for memory registration") did
the first important step of utilizing a new rdma API so addresses
translation is no longer needed.
This patch-set continues and remove entirely the processing in data-path by
eliminating the need to translate emulated mr_id to backend device mr_id.

v0 -> v1:
	* Accept comment from Marcel

Yuval Shaia (2):
  hw/rdma: Cosmetic change - no need for two sge arrays
  hw/rdma: Skip data-path mr_id translation

 hw/rdma/rdma_backend.c | 61 +++++++++++++++++++++---------------------
 hw/rdma/rdma_backend.h |  5 ----
 hw/rdma/rdma_rm.c      | 13 +++++----
 3 files changed, 36 insertions(+), 43 deletions(-)

-- 
2.20.1



             reply	other threads:[~2020-03-20 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 14:34 Yuval Shaia [this message]
2020-03-20 14:34 ` [PATCH v1 1/2] hw/rdma: Cosmetic change - no need for two sge arrays Yuval Shaia
2020-03-21 16:50   ` Marcel Apfelbaum
2020-03-20 14:34 ` [PATCH v1 2/2] hw/rdma: Skip data-path mr_id translation Yuval Shaia
2020-03-21 16:51   ` Marcel Apfelbaum

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=20200320143429.9490-1-yuval.shaia.ml@gmail.com \
    --to=yuval.shaia.ml@gmail.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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).