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>,
Junichi Nomura <j-nomura@ce.jp.nec.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
Heinz Mauelshagen <heinzm@redhat.com>
Subject: [git pull] device mapper changes for 3.18
Date: Fri, 17 Oct 2014 15:11:45 -0400 [thread overview]
Message-ID: <20141017191144.GA26800@redhat.com> (raw)
Hi Linus,
I rebased the DM tree ontop of linux-block.git's 'for-3.18/core' at the
beginning of October because DM core now depends on the newly introduced
bioset_create_nobvec() interface.
The following changes since commit d8f429e1669b9709f5b669aac9d734dbe0640891:
block: add bioset_create_nobvec() (2014-10-03 15:28:18 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/dm-3.18
for you to fetch changes up to 56ec16cb1e1ce46354de8511eef962a417c32c92:
dm log userspace: fix memory leak in dm_ulog_tfr_init failure path (2014-10-05 20:03:38 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
. fix DM's long-standing excessive use of memory by leveraging the new
bioset_create_nobvec() interface when creating the DM's bioset
. fix a few bugs in dm-bufio and dm-log-userspace
. add DM core support for a DM multipath use-case that requires loading
DM tables that contain devices that have failed (by allowing active
and inactive DM tables to share dm_devs)
. add discard support to the DM raid target; like MD raid456 the user
must opt-in to raid456 discard support be specifying the
devices_handle_discard_safely=Y module param.
----------------------------------------------------------------
Alexey Khoroshilov (1):
dm log userspace: fix memory leak in dm_ulog_tfr_init failure path
Benjamin Marzinski (2):
dm mpath: stop queueing IO when no valid paths exist
dm: allow active and inactive tables to share dm_devs
Heinz Mauelshagen (2):
dm raid: add discard support for RAID levels 1 and 10
dm raid: add discard support for RAID levels 4, 5 and 6
Joe Thornber (1):
dm bufio: update last_accessed when relinking a buffer
Junichi Nomura (2):
dm: remove nr_iovecs parameter from alloc_tio()
dm: use bioset_create_nobvec()
Mikulas Patocka (1):
dm bufio: when done scanning return from __scan immediately
drivers/md/dm-bufio.c | 5 +-
drivers/md/dm-ioctl.c | 2 +-
drivers/md/dm-log-userspace-transfer.c | 2 +-
drivers/md/dm-mpath.c | 4 +-
drivers/md/dm-raid.c | 60 +++++++++++++-
drivers/md/dm-table.c | 102 ++++++++---------------
drivers/md/dm.c | 143 ++++++++++++++++++++++++++++++---
drivers/md/dm.h | 5 +-
include/uapi/linux/dm-ioctl.h | 4 +-
9 files changed, 238 insertions(+), 89 deletions(-)
reply other threads:[~2014-10-17 19:12 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=20141017191144.GA26800@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=heinzm@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=khoroshilov@ispras.ru \
--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 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).