All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
	Mikulas Patocka <mpatocka@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>,
	Ondrej Kozina <okozina@redhat.com>, Milan Broz <mbroz@redhat.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: [git pull] additional device mapper changes for 3.20
Date: Fri, 20 Feb 2015 10:48:26 -0500	[thread overview]
Message-ID: <20150220154825.GA21338@redhat.com> (raw)
In-Reply-To: <20150216210142.GA22223@redhat.com>

Hi Linus,

The following changes since commit 802ea9d8645d33d24b7b4cd4537c14f3e698bde0:

  Merge tag 'dm-3.20-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm (2015-02-12 16:36:31 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/dm-3.20-changes-2

for you to fetch changes up to 22aa66a3ee5b61e0f4a0bfeabcaa567861109ec3:

  dm snapshot: fix a possible invalid memory access on unload (2015-02-18 09:41:54 -0500)

----------------------------------------------------------------
- Significant dm-crypt CPU scalability performance improvements thanks
  to changes that enable effective use of an unbound workqueue across
  all available CPUs.  A large battery of tests were performed to
  validate these changes, summary of results is available here:
  https://www.redhat.com/archives/dm-devel/2015-February/msg00106.html

- A few additional stable fixes (to DM core, dm-snapshot and dm-mirror)
  and a small fix to the dm-space-map-disk.

----------------------------------------------------------------
Darrick J. Wong (1):
      dm io: reject unsupported DISCARD requests with EOPNOTSUPP

Mike Snitzer (1):
      dm space map disk: fix sm_disk_count_is_more_than_one()

Mikulas Patocka (10):
      dm mirror: do not degrade the mirror on discard error
      dm crypt: use unbound workqueue for request processing
      dm crypt: don't allocate pages for a partial request
      dm crypt: avoid deadlock in mempools
      dm crypt: remove unused io_pool and _crypt_io_pool
      dm crypt: offload writes to thread
      dm crypt: add 'submit_from_crypt_cpus' option
      dm crypt: sort writes
      dm: fix a race condition in dm_get_md
      dm snapshot: fix a possible invalid memory access on unload

 Documentation/device-mapper/dm-crypt.txt       |  15 +-
 drivers/md/dm-crypt.c                          | 392 ++++++++++++++-----------
 drivers/md/dm-io.c                             |   6 +
 drivers/md/dm-raid1.c                          |   9 +
 drivers/md/dm-snap.c                           |   4 +-
 drivers/md/dm.c                                |  27 +-
 drivers/md/persistent-data/dm-space-map-disk.c |   4 +-
 7 files changed, 269 insertions(+), 188 deletions(-)

      reply	other threads:[~2015-02-20 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 14:13 [git pull] device mapper changes for 3.16 Mike Snitzer
2015-02-16 21:01 ` targeting dm-crypt cpu scalability changes for 3.20 still [was: Re: [git pull] device mapper changes for 3.16] Mike Snitzer
2015-02-20 15:48   ` Mike Snitzer [this message]

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=20150220154825.GA21338@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=okozina@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.