Please pull from:
 
  git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm tags/dm-3.7-changes
 
to get the following device-mapper changes for 3.7.

Thanks,
Alasdair

----------------------------------------------------------------
Remove the power-of-2 block size constraint on discards in dm thin
provisioning and factor the bio_prison code out into a separate
module (for sharing with the forthcoming cache target).

Use struct bio's front_pad to eliminate the use of one separate mempool
by bio-based devices.

A few other tiny clean-ups.

----------------------------------------------------------------
Mike Snitzer (3):
      dm thin: support discard with non power of two block size
      dm thin: prepare to separate bio_prison code
      dm thin: move bio_prison code to separate module

Mikulas Patocka (2):
      dm: use ACCESS_ONCE for sysfs values
      dm: store dm_target_io in bio front_pad

Wei Yongjun (3):
      dm mpath: fix check for null mpio in end_io fn
      dm bufio: use list_move
      dm persistent data: convert to use le32_add_cpu

 drivers/md/Kconfig                               |    8 +
 drivers/md/Makefile                              |    1 +
 drivers/md/dm-bio-prison.c                       |  415 +++++++++++++++++
 drivers/md/dm-bio-prison.h                       |   72 +++
 drivers/md/dm-bufio.c                            |   13 +-
 drivers/md/dm-mpath.c                            |    3 +-
 drivers/md/dm-thin.c                             |  521 ++++------------------
 drivers/md/dm-verity.c                           |    2 +-
 drivers/md/dm.c                                  |  108 ++---
 drivers/md/persistent-data/dm-space-map-common.c |    4 +-
 10 files changed, 636 insertions(+), 511 deletions(-)
 create mode 100644 drivers/md/dm-bio-prison.c
 create mode 100644 drivers/md/dm-bio-prison.h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to