From: Thanos Makatos <thanos.makatos@onapp.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: heinzm@redhat.com, thornber@redhat.com,
Mike Snitzer <snitzer@redhat.com>
Subject: dm-cache suspend semantics
Date: Wed, 19 Aug 2015 12:26:20 +0100 [thread overview]
Message-ID: <CAM2wQBsvnY+eBMxEFRy07f=16XnYmcdVQOewo-DWBseSnqAR9g@mail.gmail.com> (raw)
I'd like to know whether it is possible for a cache target for which
there are dirty blocks to continue writing back dirty data after it
has been suspended. Can this happen? I checked the code and
cache_postsuspend() suggests that after the target is suspended no
write back I/O will be initiated (I also did a quick test that
confirms this), however I'd appreciate an answer from the maintainers
as I might have misunderstood.
--
Thanos Makatos
next reply other threads:[~2015-08-19 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 11:26 Thanos Makatos [this message]
2015-08-19 18:42 ` dm-cache suspend semantics Alasdair G Kergon
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='CAM2wQBsvnY+eBMxEFRy07f=16XnYmcdVQOewo-DWBseSnqAR9g@mail.gmail.com' \
--to=thanos.makatos@onapp.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@redhat.com \
--cc=snitzer@redhat.com \
--cc=thornber@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).