dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Thanos Makatos <thanos.makatos@onapp.com>
Cc: heinzm@redhat.com,
	device-mapper development <dm-devel@redhat.com>,
	thornber@redhat.com, Mike Snitzer <snitzer@redhat.com>
Subject: Re: dm-cache suspend semantics
Date: Wed, 19 Aug 2015 19:42:05 +0100	[thread overview]
Message-ID: <20150819184204.GC18567@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <CAM2wQBsvnY+eBMxEFRy07f=16XnYmcdVQOewo-DWBseSnqAR9g@mail.gmail.com>

On Wed, Aug 19, 2015 at 12:26:20PM +0100, Thanos Makatos wrote:
> 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?

A suspended device-mapper device must not generate any I/O to the
devices underneath it while it is suspended.

Alasdair

      reply	other threads:[~2015-08-19 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 11:26 dm-cache suspend semantics Thanos Makatos
2015-08-19 18:42 ` Alasdair G Kergon [this message]

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=20150819184204.GC18567@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=heinzm@redhat.com \
    --cc=snitzer@redhat.com \
    --cc=thanos.makatos@onapp.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).