From: Mike Christie <michael.christie@oracle.com>
To: virtualization@lists.linux-foundation.org, jasowang@redhat.com,
pbonzini@redhat.com, mst@redhat.com, stefanha@redhat.com
Subject: [PATCH 0/2] vhost-scsi: IO virtqueue creation fixes/features
Date: Thu, 7 Jul 2022 22:05:23 -0500 [thread overview]
Message-ID: <20220708030525.5065-1-michael.christie@oracle.com> (raw)
The following patches were made over Linus's tree but apply over mst's
next/vhost branches. They fix an issue where userspace calculates the
number of virtqueues differently than the kernel and allows userspace
to control the max number of queues.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next reply other threads:[~2022-07-08 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 3:05 Mike Christie [this message]
2022-07-08 3:05 ` [PATCH 1/2] vhost-scsi: Fix max number of virtqueues Mike Christie
2022-07-14 6:51 ` Jason Wang
2022-07-08 3:05 ` [PATCH 2/2] vhost scsi: Allow user to control num virtqueues Mike Christie
2022-07-15 3:40 ` 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=20220708030525.5065-1-michael.christie@oracle.com \
--to=michael.christie@oracle.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.