From: "Eugenio Pérez" <eperezma@redhat.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
linux-kernel@vger.kernel.org,
German Maglione <gmaglione@redhat.com>,
virtualization@lists.linux.dev,
Stefano Garzarella <sgarzare@redhat.com>,
yama@redhat.com, Vivek Goyal <vgoyal@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
mst@redhat.com, Jason Wang <jasowang@redhat.com>
Subject: [RFC v2 4/5] virtiofs: perform DMA operations out of the spinlock
Date: Fri, 21 Feb 2025 18:06:25 +0100 [thread overview]
Message-ID: <20250221170626.261687-5-eperezma@redhat.com> (raw)
In-Reply-To: <20250221170626.261687-1-eperezma@redhat.com>
This is useful for some setups like swiotlb or VDUSE where the DMA
operations are expensive and/or need to be performed with a write lock.
After applying this patch, fio read test goes from 1124MiB/s to 1191MiB/s.
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
fs/fuse/virtio_fs.c | 40 ++++++++++++++++++++++++++++++++++++++--
1 file changed, 38 insertions(+), 2 deletions(-)
diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/virtio_fs.c
index 1344c5782a7c..e19c78f2480e 100644
--- a/fs/fuse/virtio_fs.c
+++ b/fs/fuse/virtio_fs.c
@@ -836,8 +836,19 @@ static void virtio_fs_requests_done_work(struct work_struct *work)
/* End requests */
list_for_each_entry_safe(req, next, &reqs, list) {
+ unsigned int total_sgs = req->out_sgs + req->in_sgs;
+
list_del_init(&req->list);
+ for (unsigned int i = 0; i < total_sgs; ++i) {
+ enum dma_data_direction dir = (i < req->out_sgs) ?
+ DMA_TO_DEVICE : DMA_FROM_DEVICE;
+ dma_unmap_page(vq->vdev->dev.parent,
+ sg_dma_address(&req->sg[i]),
+ sg_dma_len(&req->sg[i]), dir);
+
+ }
+
/* blocking async request completes in a worker context */
if (req->args->may_block) {
struct virtio_fs_req_work *w;
@@ -1426,6 +1437,24 @@ static int virtio_fs_enqueue_req(struct virtio_fs_vq *fsvq,
sgs[i] = &req->sg[i];
WARN_ON(req->out_sgs + req->in_sgs != total_sgs);
+ // TODO can we change this ptr out of the lock?
+ vq = fsvq->vq;
+ // TODO handle this and following errors
+ for (i = 0; i < total_sgs; i++) {
+ struct page *page = sg_page(&req->sg[i]);
+ enum dma_data_direction dir = (i < req->out_sgs) ?
+ DMA_TO_DEVICE : DMA_FROM_DEVICE;
+ dma_addr_t dma_addr = dma_map_page(vq->vdev->dev.parent, page,
+ req->sg[i].offset, req->sg[i].length, dir);
+
+ if (dma_mapping_error(vq->vdev->dev.parent, dma_addr)) {
+ ret = -ENOMEM;
+ goto out;
+ }
+ sg_dma_address(&req->sg[i]) = dma_addr;
+ sg_dma_len(&req->sg[i]) = req->sg[i].length;
+ }
+
spin_lock(&fsvq->lock);
if (!fsvq->connected) {
@@ -1434,8 +1463,8 @@ static int virtio_fs_enqueue_req(struct virtio_fs_vq *fsvq,
goto out;
}
- vq = fsvq->vq;
- ret = virtqueue_add_sgs(vq, sgs, req->out_sgs, req->in_sgs, req, GFP_ATOMIC);
+ ret = virtqueue_add_sgs_premapped(vq, sgs, req->out_sgs,
+ req->in_sgs, req, GFP_ATOMIC);
if (ret < 0) {
spin_unlock(&fsvq->lock);
goto out;
@@ -1460,6 +1489,13 @@ static int virtio_fs_enqueue_req(struct virtio_fs_vq *fsvq,
virtqueue_notify(vq);
out:
+ for (unsigned int j = 0; ret && j < total_sgs; ++j) {
+ enum dma_data_direction dir = (j < req->out_sgs) ?
+ DMA_TO_DEVICE : DMA_FROM_DEVICE;
+ dma_unmap_page(vq->vdev->dev.parent,
+ sg_dma_address(&req->sg[j]),
+ sg_dma_len(&req->sg[j]), dir);
+ }
if (ret < 0 && req->argbuf) {
kfree(req->argbuf);
req->argbuf = NULL;
--
2.48.1
next prev parent reply other threads:[~2025-02-21 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 17:06 [RFC v2 0/5] virtiofs: map buffer out of virtqueue lock Eugenio Pérez
2025-02-21 17:06 ` [RFC v2 1/5] vduse: add virtio_fs to allowed dev id Eugenio Pérez
2025-02-24 1:57 ` Jason Wang
2025-02-24 6:42 ` Eugenio Perez Martin
2025-02-21 17:06 ` [RFC v2 2/5] virtiofs: Move stack sg to fuse_req Eugenio Pérez
2025-02-21 17:06 ` [RFC v2 3/5] virtio_ring: add api for premapped out and in buffer chain Eugenio Pérez
2025-02-21 17:06 ` Eugenio Pérez [this message]
2025-02-24 2:03 ` [RFC v2 4/5] virtiofs: perform DMA operations out of the spinlock Jason Wang
2025-02-21 17:06 ` [RFC v2 5/5] virtiofs: Disable notifications more aggresively Eugenio Pérez
2025-02-24 2:01 ` Jason Wang
2025-02-24 6:44 ` Eugenio Perez Martin
2025-02-24 7:44 ` Eugenio Perez Martin
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=20250221170626.261687-5-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=gmaglione@redhat.com \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yama@redhat.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).