linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Connor Kuehl <ckuehl@redhat.com>
To: virtio-fs@redhat.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, stefanha@redhat.com,
	vgoyal@redhat.com, miklos@szeredi.hu, jasowang@redhat.com,
	mst@redhat.com
Subject: [PATCH 0/3] virtiofs: split requests that exceed virtqueue size
Date: Thu, 18 Mar 2021 08:52:20 -0500	[thread overview]
Message-ID: <20210318135223.1342795-1-ckuehl@redhat.com> (raw)

I also have a patch in this series that fixes a typo I saw while I was
in there.

For testing, I have been using a toy program that performs a readv or a
writev with a large number of iovecs that exceeds the number of
descriptors available to the virtqueue and observing the number of
scattergather lists generated don't exceed the size of the virtqueue.

Connor Kuehl (3):
  virtio_ring: always warn when descriptor chain exceeds queue size
  virtiofs: split requests that exceed virtqueue size
  fuse: fix typo for fuse_conn.max_pages comment

 drivers/virtio/virtio_ring.c |  7 ++++---
 fs/fuse/fuse_i.h             |  7 ++++++-
 fs/fuse/inode.c              |  7 +++++++
 fs/fuse/virtio_fs.c          | 14 ++++++++++++++
 4 files changed, 31 insertions(+), 4 deletions(-)

-- 
2.30.2


             reply	other threads:[~2021-03-18 13:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 13:52 Connor Kuehl [this message]
2021-03-18 13:52 ` [PATCH 1/3] virtio_ring: always warn when descriptor chain exceeds queue size Connor Kuehl
2021-03-22  3:22   ` Jason Wang
2021-03-22  8:17     ` Michael S. Tsirkin
2021-03-23  2:38       ` Jason Wang
2021-03-18 13:52 ` [PATCH 2/3] virtiofs: split requests that exceed virtqueue size Connor Kuehl
2021-03-18 15:17   ` Miklos Szeredi
2021-03-18 15:52     ` Connor Kuehl
2021-03-20 20:04       ` Michael S. Tsirkin
2021-03-22 19:01     ` Vivek Goyal
2021-03-24 15:09     ` Connor Kuehl
2021-03-24 15:30       ` Miklos Szeredi
2021-03-24 15:31         ` Connor Kuehl
2021-03-19 13:49   ` Vivek Goyal
2021-03-19 14:16     ` Connor Kuehl
2021-03-22 15:47   ` Stefan Hajnoczi
2021-03-18 13:52 ` [PATCH 3/3] fuse: fix typo for fuse_conn.max_pages comment Connor Kuehl
2021-03-22  3:42   ` Jason Wang

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=20210318135223.1342795-1-ckuehl@redhat.com \
    --to=ckuehl@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mst@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vgoyal@redhat.com \
    --cc=virtio-fs@redhat.com \
    --cc=virtualization@lists.linux-foundation.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).