From: "Denis V. Lunev" <den@openvz.org>
To: qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: den@openvz.org, Evgeny Yakovlev <eyakovlev@virtuozzo.com>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Fam Zheng <famz@redhat.com>, John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH v7 0/4] block: ignore flush requests when storage is clean
Date: Fri, 15 Jul 2016 16:47:25 +0300 [thread overview]
Message-ID: <1468590449-25465-1-git-send-email-den@openvz.org> (raw)
Changes from v6:
- squashed patches 5-6 into patch 4 to avoid test faults on git bissect
- changed sector number from 0 to 1 in patch 3
Changes from v5:
- Removed failed flush traces in block tests 026 071 089
- Changed BLOCK_JOB_READY event order in block tests 141 144
Changes from v4:
- Moved to write generation scheme instead of dirty flag
- Added retry setup to IDE PIO and FLUSH requests
Changes from v3:
- Fixed a typo in commit message
- Rebased on Kevin'n origin/block
Changes from v2:
- Better comments
- Rebased on latest master
Changes from v1:
- Flush requests that should be skipped will now wait for completion
of any previous requests already in flight
- Fixed IDE and AHCI tests to dirty media for new flush behaviour
- Fixed a problem in IDE CMD_FLUSH_CACHE failure handling
Signed-off-by: Evgeny Yakovlev <eyakovlev@virtuozzo.com>
Signed-off-by: Denis V. Lunev <den@openvz.org>
CC: Kevin Wolf <kwolf@redhat.com>
CC: Max Reitz <mreitz@redhat.com>
CC: Stefan Hajnoczi <stefanha@redhat.com>
CC: Fam Zheng <famz@redhat.com>
CC: John Snow <jsnow@redhat.com>
Evgeny Yakovlev (4):
ide: refactor retry_unit set and clear into separate function
ide: set retry_unit for PIO and FLUSH requests
tests: in IDE and AHCI tests perform DMA write before flushing
block: ignore flush requests when storage is clean
block.c | 3 +++
block/io.c | 21 ++++++++++++++++
hw/ide/core.c | 24 +++++++++++++-----
include/block/block_int.h | 5 ++++
tests/ahci-test.c | 34 ++++++++++++++++++++++++--
tests/ide-test.c | 43 ++++++++++++++++++++++++++++++++
tests/qemu-iotests/026.out.nocache | 50 --------------------------------------
tests/qemu-iotests/071.out | 8 ------
tests/qemu-iotests/089.out | 2 --
tests/qemu-iotests/141.out | 4 +--
tests/qemu-iotests/144.out | 2 +-
11 files changed, 125 insertions(+), 71 deletions(-)
--
2.1.4
next reply other threads:[~2016-07-15 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 13:47 Denis V. Lunev [this message]
2016-07-15 13:47 ` [Qemu-devel] [PATCH v7 1/4] ide: refactor retry_unit set and clear into separate function Denis V. Lunev
2016-07-15 13:47 ` [Qemu-devel] [PATCH v7 2/4] ide: set retry_unit for PIO and FLUSH requests Denis V. Lunev
2016-07-15 13:47 ` [Qemu-devel] [PATCH v7 3/4] tests: in IDE and AHCI tests perform DMA write before flushing Denis V. Lunev
2016-07-15 13:47 ` [Qemu-devel] [PATCH v7 4/4] block: ignore flush requests when storage is clean Denis V. Lunev
2016-07-18 19:10 ` John Snow
2016-07-18 19:17 ` Denis V. Lunev
2016-07-18 19:18 ` John Snow
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=1468590449-25465-1-git-send-email-den@openvz.org \
--to=den@openvz.org \
--cc=eyakovlev@virtuozzo.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).