Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: dm-devel@redhat.com
Cc: ejt@redhat.com
Subject: [PATCH 0/3] dm thin metadata: handful of improvements
Date: Mon, 15 Apr 2019 17:17:14 -0400	[thread overview]
Message-ID: <20190415211717.18737-1-snitzer@redhat.com> (raw)

All are working well in my testing but I'd appreciate further review
from others.

Thanks,
Mike

Mike Snitzer (3):
  dm space map common: zero entire ll_disk
  dm thin metadata: do not write metadata if no changes occurred
  dm thin metadata: check __commit_transaction()'s return

 drivers/md/dm-thin-metadata.c                 | 63 +++++++++++++------
 .../md/persistent-data/dm-space-map-common.c  |  2 +
 2 files changed, 47 insertions(+), 18 deletions(-)

-- 
2.18.0

             reply	other threads:[~2019-04-15 21:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 21:17 Mike Snitzer [this message]
2019-04-15 21:17 ` [PATCH 1/3] dm space map common: zero entire ll_disk Mike Snitzer
2019-04-15 21:17 ` [PATCH 2/3] dm thin metadata: do not write metadata if no changes occurred Mike Snitzer
2019-04-16  2:39   ` Mike Snitzer
2019-04-17  1:30     ` [PATCH v2 " Mike Snitzer
2019-04-15 21:17 ` [PATCH 3/3] dm thin metadata: check __commit_transaction()'s return Mike Snitzer

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=20190415211717.18737-1-snitzer@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@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