From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Bryan Gurney <bgurney@redhat.com>,
Dmitry Fomichev <dmitry.fomichev@wdc.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Heinz Mauelshagen <heinzm@redhat.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Maged Mokhtar <mmokhtar@petasan.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Nikos Tsironis <ntsironis@arrikto.com>
Subject: [git pull] device mapper changes for 5.5
Date: Fri, 22 Nov 2019 10:37:47 -0500 [thread overview]
Message-ID: <20191122153747.GA23143@redhat.com> (raw)
Hi Linus,
The following changes since commit a99d8080aaf358d5d23581244e5da23b35e340b9:
Linux 5.4-rc6 (2019-11-03 14:07:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.5/dm-changes
for you to fetch changes up to f612b2132db529feac4f965f28a1b9258ea7c22b:
Revert "dm crypt: use WQ_HIGHPRI for the IO and crypt workqueues" (2019-11-20 17:27:39 -0500)
Please pull, thanks!
Mike
----------------------------------------------------------------
- Fix DM core to disallow stacking request-based DM on partitions.
- Fix DM raid target to properly resync raidset even if bitmap needed
additional pages.
- Fix DM crypt performance regression due to use of WQ_HIGHPRI for the
IO and crypt workqueues.
- Fix DM integrity metadata layout that was aligned on 128K boundary
rather than the intended 4K boundary (removes 124K of wasted space for
each metadata block).
- Improve the DM thin, cache and clone targets to use spin_lock_irq
rather than spin_lock_irqsave where possible.
- Fix DM thin single thread performance that was lost due to needless
workqueue wakeups.
- Fix DM zoned target performance that was lost due to excessive backing
device checks.
- Add ability to trigger write failure with the DM dust test target.
- Fix whitespace indentation in drivers/md/Kconfig.
- Various smalls fixes and cleanups (e.g. use struct_size, fix
uninitialized variable, variable renames, etc).
----------------------------------------------------------------
Bryan Gurney (3):
dm dust: change result vars to r
dm dust: change ret to r in dust_map_read and dust_map
dm dust: add limited write failure mode
Dmitry Fomichev (1):
dm zoned: reduce overhead of backing device checks
Gustavo A. R. Silva (1):
dm stripe: use struct_size() in kmalloc()
Heinz Mauelshagen (4):
dm raid: change rs_set_dev_and_array_sectors API and callers
dm raid: to ensure resynchronization, perform raid set grow in preresume
dm raid: simplify rs_setup_recovery call chain
dm raid: streamline rs_get_progress() and its raid_status() caller side
Jeffle Xu (1):
dm thin: wakeup worker only when deferred bios exist
Krzysztof Kozlowski (1):
dm: Fix Kconfig indentation
Maged Mokhtar (1):
dm writecache: handle REQ_FUA
Mike Snitzer (2):
dm table: do not allow request-based DM to stack on partitions
Revert "dm crypt: use WQ_HIGHPRI for the IO and crypt workqueues"
Mikulas Patocka (6):
dm writecache: fix uninitialized variable warning
dm clone: replace spin_lock_irqsave with spin_lock_irq
dm thin: replace spin_lock_irqsave with spin_lock_irq
dm bio prison: replace spin_lock_irqsave with spin_lock_irq
dm cache: replace spin_lock_irqsave with spin_lock_irq
dm integrity: fix excessive alignment of metadata runs
Nathan Chancellor (1):
dm raid: Remove unnecessary negation of a shift in raid10_format_to_md_layout
Nikos Tsironis (1):
dm clone: add bucket_lock_irq/bucket_unlock_irq helpers
.../admin-guide/device-mapper/dm-integrity.rst | 5 +
.../admin-guide/device-mapper/dm-raid.rst | 2 +
drivers/md/Kconfig | 54 +++----
drivers/md/dm-bio-prison-v1.c | 27 ++--
drivers/md/dm-bio-prison-v2.c | 26 ++--
drivers/md/dm-cache-target.c | 77 ++++------
drivers/md/dm-clone-metadata.c | 29 ++--
drivers/md/dm-clone-metadata.h | 4 +-
drivers/md/dm-clone-target.c | 62 ++++----
drivers/md/dm-crypt.c | 9 +-
drivers/md/dm-dust.c | 97 ++++++++----
drivers/md/dm-integrity.c | 28 +++-
drivers/md/dm-raid.c | 164 +++++++++++----------
drivers/md/dm-stripe.c | 15 +-
drivers/md/dm-table.c | 27 +---
drivers/md/dm-thin.c | 118 +++++++--------
drivers/md/dm-writecache.c | 5 +-
drivers/md/dm-zoned-metadata.c | 29 ++--
drivers/md/dm-zoned-reclaim.c | 8 +-
drivers/md/dm-zoned-target.c | 54 +++++--
drivers/md/dm-zoned.h | 2 +
include/linux/device-mapper.h | 3 -
22 files changed, 433 insertions(+), 412 deletions(-)
next reply other threads:[~2019-11-22 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 15:37 Mike Snitzer [this message]
2019-11-25 22:45 ` [git pull] device mapper changes for 5.5 pr-tracker-bot
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=20191122153747.GA23143@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=bgurney@redhat.com \
--cc=dm-devel@redhat.com \
--cc=dmitry.fomichev@wdc.com \
--cc=gustavo@embeddedor.com \
--cc=heinzm@redhat.com \
--cc=jefflexu@linux.alibaba.com \
--cc=krzk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mmokhtar@petasan.org \
--cc=mpatocka@redhat.com \
--cc=natechancellor@gmail.com \
--cc=ntsironis@arrikto.com \
--cc=torvalds@linux-foundation.org \
/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).