From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Anton Nefedov <anton.nefedov@virtuozzo.com>,
Alberto Garcia <berto@igalia.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Subject: [Qemu-devel] [RFC 0/3] block: Inquire images’ rotational info
Date: Fri, 24 May 2019 19:28:09 +0200 [thread overview]
Message-ID: <20190524172812.27308-1-mreitz@redhat.com> (raw)
Hi,
http://lists.nongnu.org/archive/html/qemu-block/2019-05/msg00569.html
shows that optimizations affect HDDs and SSDs differently. It would be
nice if we could differentiate between the two and then choose to adjust
our behavior depending on whether a given image is stored on an HDD or
not.
Or maybe it isn’t so nice. That’s one reason this is an RFC.
The other is that I implemented recognition of the rotational status by
querying sysfs. That looks stupid, but I didn’t find a better way
(there is a BLKROTATIONAL ioctl, but that only works on device files).
But, hey, if you look through block/file-posix.c, you’ll find that I’m
not the first to query sysfs. hdev_get_max_segments() does so, too. So
maybe it isn’t that bad of an idea.
What do you think? Is the whole idea stupid? Just the implementation?
Or does it make sense?
Max Reitz (3):
block: Add ImageRotationalInfo
file-posix: Inquire rotational status
qcow2: Evaluate rotational info
qapi/block-core.json | 19 ++++++++++-
block/qcow2.h | 3 ++
include/block/block.h | 7 +++++
block.c | 20 +++++++++++-
block/file-posix.c | 73 +++++++++++++++++++++++++++++++++++++++++++
block/qapi.c | 3 ++
block/qcow2.c | 34 +++++++++++++++++---
7 files changed, 153 insertions(+), 6 deletions(-)
--
2.21.0
next reply other threads:[~2019-05-24 17:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 17:28 Max Reitz [this message]
2019-05-24 17:28 ` [Qemu-devel] [RFC 1/3] block: Add ImageRotationalInfo Max Reitz
2019-05-26 15:08 ` Alberto Garcia
2019-05-27 12:16 ` Max Reitz
2019-05-27 12:37 ` Alberto Garcia
2019-05-27 12:57 ` Max Reitz
2019-05-27 13:44 ` Anton Nefedov
2019-05-27 13:51 ` Max Reitz
2019-05-27 13:53 ` Alberto Garcia
2019-05-29 22:10 ` Kevin Wolf
2019-05-31 11:51 ` Max Reitz
2019-05-31 14:02 ` Kevin Wolf
2019-05-24 17:28 ` [Qemu-devel] [RFC 2/3] file-posix: Inquire rotational status Max Reitz
2019-05-24 17:28 ` [Qemu-devel] [RFC 3/3] qcow2: Evaluate rotational info Max Reitz
2019-05-24 17:52 ` [Qemu-devel] [RFC 0/3] block: Inquire images’ " Eric Blake
2019-06-13 16:12 ` Stefan Hajnoczi
2019-06-13 16:20 ` Max Reitz
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=20190524172812.27308-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).