From: Maxim Levitsky <mlevitsk@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
qemu-block@nongnu.org, Peter Lieven <pl@kamp.de>,
Tom Yan <tom.ty89@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [PATCH v3 2/5] file-posix: add sg_get_max_segments that actually works with sg
Date: Thu, 17 Dec 2020 18:56:09 +0200 [thread overview]
Message-ID: <20201217165612.942849-3-mlevitsk@redhat.com> (raw)
In-Reply-To: <20201217165612.942849-1-mlevitsk@redhat.com>
From: Tom Yan <tom.ty89@gmail.com>
sg devices have different major/minor than their corresponding
block devices. Using sysfs to get max segments never really worked
for them.
Fortunately the sg driver provides an ioctl to get sg_tablesize,
which is apparently equivalent to max segments.
Signed-off-by: Tom Yan <tom.ty89@gmail.com>
Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
---
block/file-posix.c | 22 +++++++++++++++++++++-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/block/file-posix.c b/block/file-posix.c
index cbf1271773..2bf4d095a7 100644
--- a/block/file-posix.c
+++ b/block/file-posix.c
@@ -1179,6 +1179,26 @@ static int sg_get_max_transfer_length(int fd)
#endif
}
+static int sg_get_max_segments(int fd)
+{
+ /*
+ * /dev/sg* character devices report 'max_segments' via
+ * SG_GET_SG_TABLESIZE ioctl
+ */
+
+#ifdef SG_GET_SG_TABLESIZE
+ long max_segments = 0;
+
+ if (ioctl(fd, SG_GET_SG_TABLESIZE, &max_segments) == 0) {
+ return max_segments;
+ } else {
+ return -errno;
+ }
+#else
+ return -ENOSYS;
+#endif
+}
+
static int get_max_transfer_length(int fd)
{
#if defined(BLKSECTGET)
@@ -1265,7 +1285,7 @@ static void hdev_refresh_limits(BlockDriverState *bs, Error **errp)
bs->bl.max_transfer = pow2floor(ret);
}
- ret = get_max_segments(s->fd);
+ ret = bs->sg ? sg_get_max_segments(s->fd) : get_max_segments(s->fd);
if (ret > 0) {
bs->bl.max_transfer = MIN_NON_ZERO(bs->bl.max_transfer,
ret * qemu_real_host_page_size);
--
2.26.2
next prev parent reply other threads:[~2020-12-17 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 16:56 [PATCH v3 0/5] SCSI: fix transfer limits for SCSI passthrough Maxim Levitsky
2020-12-17 16:56 ` [PATCH v3 1/5] file-posix: split hdev_refresh_limits from raw_refresh_limits Maxim Levitsky
2021-01-07 12:24 ` Max Reitz
2020-12-17 16:56 ` Maxim Levitsky [this message]
2021-01-07 12:42 ` [PATCH v3 2/5] file-posix: add sg_get_max_segments that actually works with sg Max Reitz
2020-12-17 16:56 ` [PATCH v3 3/5] block: add max_ioctl_transfer to BlockLimits Maxim Levitsky
2021-01-07 13:09 ` Max Reitz
2020-12-17 16:56 ` [PATCH v3 4/5] block: use blk_get_max_ioctl_transfer for SCSI passthrough Maxim Levitsky
2021-01-07 13:19 ` Max Reitz
2020-12-17 16:56 ` [PATCH v3 5/5] block/scsi: correctly emulate the VPD block limits page Maxim Levitsky
2021-01-07 13:44 ` Max Reitz
2021-01-07 10:23 ` [PATCH v3 0/5] SCSI: fix transfer limits for SCSI passthrough Maxim Levitsky
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=20201217165612.942849-3-mlevitsk@redhat.com \
--to=mlevitsk@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@redhat.com \
--cc=tom.ty89@gmail.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).