From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>, Joe Thornber <ejt@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Jeff Moyer <jmoyer@redhat.com>
Subject: [git pull] device mapper changes for 3.17
Date: Wed, 13 Aug 2014 12:07:37 -0400 [thread overview]
Message-ID: <20140813160737.GA11779@redhat.com> (raw)
Hi Linus,
The following changes since commit 44fa816bb778edbab6b6ddaaf24908dd6295937e:
dm cache: fix race affecting dirty block count (2014-08-01 12:25:22 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/dm-3.17-changes
for you to fetch changes up to 200612ec33e555a356eebc717630b866ae2b694f:
dm table: propagate QUEUE_FLAG_NO_SG_MERGE (2014-08-10 20:54:49 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
. Allow the thin target to paired with any size external origin; also
allow thin snapshots to be larger than the external origin.
. Add support for quickly loading a repetitive pattern into the
dm-switch target.
. Use per-bio data in the dm-crypt target instead of always using a
mempool for each allocation. Required switching to kmalloc alignment
for the bio slab.
. Fix DM core to properly stack the QUEUE_FLAG_NO_SG_MERGE flag
. Fix the dm-cache and dm-thin targets' export of the minimum_io_size to
match the data block size -- this fixes an issue where mkfs.xfs would
improperly infer raid striping was in place on the underlying storage.
. Small cleanups in dm-io, dm-mpath and dm-cache
----------------------------------------------------------------
Jeff Moyer (1):
dm table: propagate QUEUE_FLAG_NO_SG_MERGE
Joe Thornber (5):
dm io: simplify dec_count and sync_io
dm thin: switch to an atomic_t for tracking pending new block preparations
dm thin: relax external origin size constraints
dm cache: simplify deferred set reference count increments
dm cache: fail migrations in the do_worker error path
Mike Snitzer (4):
dm mpath: eliminate pg_ready() wrapper
dm cache metadata: use dm-space-map-metadata.h defined size limits
dm thin: set minimum_io_size to pool's data block size
dm cache: set minimum_io_size to cache's data block size
Mikulas Patocka (5):
dm table: make dm_table_supports_discards static
block: use kmalloc alignment for bio slab
dm crypt: use per-bio data
dm switch: factor out switch_region_table_read
dm switch: efficiently support repetitive patterns
Documentation/device-mapper/switch.txt | 12 +++
block/bio.c | 3 +-
drivers/md/dm-cache-metadata.c | 4 +-
drivers/md/dm-cache-metadata.h | 8 +-
drivers/md/dm-cache-target.c | 128 ++++++++++++++---------
drivers/md/dm-crypt.c | 41 +++++---
drivers/md/dm-io.c | 77 +++++++-------
drivers/md/dm-mpath.c | 6 +-
drivers/md/dm-switch.c | 67 ++++++++++--
drivers/md/dm-table.c | 86 +++++++++-------
drivers/md/dm-thin.c | 181 +++++++++++++++++++++++----------
drivers/md/dm.h | 1 -
12 files changed, 408 insertions(+), 206 deletions(-)
reply other threads:[~2014-08-13 16:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140813160737.GA11779@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.