Linux Device-Mapper Development

• Thread Index

• Re: [PATCH 1/2] dm-crypt: Properly handle extra key string in initialization
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 1/1] improve the performance of dm-log-userspace
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [RFC PATCH v2] dm mpath: add a queue_if_no_path timeout
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH]dm-mpath: fix for race condition between multipath_dtr and pg_init_done.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/2] dm-crypt: Add TCW IV mode for old CBC TCRYPT containers.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] dm-crypt: Properly handle extra key string in initialization
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 17/23] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 17/23] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 17/23] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 17/23] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 12/23] block: Convert drivers to immutable biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 23/23] block: Don't save/copy bvec array anymore, share when cloning
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 17/23] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 06/23] block: Convert bio_iovec() to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 05/23] dm: Use bvec_iter for dm_bio_record()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 06/24 v2] dm cache policy mq: return NULL from alloc_entry if cache is full
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/2] dm-crypt: Properly handle extra key string in initialization
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH 2/2] dm-crypt: Add TCW IV mode for old CBC TCRYPT containers.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• generic_make_request() sleep
  • From: siju george <siju.george@xxxxxxxxx>
• Re: [PATCH 2/2] dm-crypt: Add TCW IV mode for old CBC TCRYPT containers.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH 1/2] dm-crypt: Properly handle extra key string in initialization
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [PATCH 2/2] dm-crypt: Add TCW IV mode for old CBC TCRYPT containers.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] dm-crypt: Properly handle extra key string in initialization
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/1] improve the performance of dm-log-userspace
  • From: dongmao zhang <dmzhang@xxxxxxxx>
• [PATCH 0/1] patches to improve cluster raid1 performance [V3]
  • From: dongmao zhang <dmzhang@xxxxxxxx>
• [PATCH] New userspace statistics patch
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [BUG 3.12.rc4] Oops: unable to handle kernel paging request during shutdown
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 21/24] dm cache: add trc policy shim
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 06/24] dm cache policy mq: return NULL if mq->free list is empty in alloc_entry
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 21/24] dm cache: add trc policy shim
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 06/24] dm cache policy mq: return NULL if mq->free list is empty in alloc_entry
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 21/24] dm cache: add trc policy shim
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 14/24] dm cache: use is_write_io() in more places
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 11/24] dm table: print error on preresume failure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 09/24] dm cache metadata: check the metadata version when reading the superblock
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 14/24] dm cache: use is_write_io() in more places
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 01/24] dm: nest targets used for testing under DM_TEST_TARGETS
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 01/24] dm: nest targets used for testing under DM_TEST_TARGETS
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 11/24] dm table: print error on preresume failure
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 05/24] dm cache policy mq: implement writeback_work() and mq_{set, clear}_dirty()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 09/24] dm cache metadata: check the metadata version when reading the superblock
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 06/24] dm cache policy mq: return NULL if mq->free list is empty in alloc_entry
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 05/24] dm cache policy mq: implement writeback_work() and mq_{set, clear}_dirty()
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] multipathd: revert mpp size update if map update fails
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH] multipathd: revert mpp size update if map update fails
  • From: michaelc@xxxxxxxxxxx
• Re: [PATCH 01/24] dm: nest targets used for testing under DM_TEST_TARGETS
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 01/24] dm: nest targets used for testing under DM_TEST_TARGETS
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH 23/24] dm cache: add cache block invalidation API
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 08/24] dm cache metadata: return bool from __superblock_all_zeroes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 07/24] dm cache: be much more aggressive about promoting writes to discarded blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 15/24] dm cache: use cell_defer() boolean argument consistently
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 19/24] dm cache: support for stackable caching policies
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 05/24] dm cache policy mq: implement writeback_work() and mq_{set, clear}_dirty()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 13/24] dm cache policy: have policy_writeback_work return -ENODATA by default
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 02/24] dm space map disk: optimise sm_disk_dec_block
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 21/24] dm cache: add trc policy shim
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 10/24] dm cache policy: variable hints support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 12/24] dm cache: add passthrough mode
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 14/24] dm cache: use is_write_io() in more places
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 04/24] dm cache policy mq: a few small fixes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 01/24] dm: nest targets used for testing under DM_TEST_TARGETS
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 03/24] dm cache policy: remove return from void policy_remove_mapping
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 06/24] dm cache policy mq: return NULL if mq->free list is empty in alloc_entry
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 20/24] dm cache: add era policy shim
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 24/24] dm cache policy era: add cache block invalidation support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 22/24] dm cache: add hints policy
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 17/24] dm cache: use a boolean when setting cache->quiescing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 18/24] dm cache: optimize commit_if_needed
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 16/24] dm cache: log error message if dm_kcopyd_copy() fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 11/24] dm table: print error on preresume failure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 09/24] dm cache metadata: check the metadata version when reading the superblock
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 00/24] dm cache: proposed changes for v3.13 merge
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Volume group / volumes not activated at boot
  • From: David Rosenstrauch <darose@xxxxxxxxxx>
• Re: Volume group / volumes not activated at boot
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Volume group / volumes not activated at boot
  • From: David Rosenstrauch <darose@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• kpartx ignores read-only?
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Prakash Prasad <prakash_prasad@xxxxxxxxx>
• [PATCH]dm-mpath: fix for race condition between multipath_dtr and pg_init_done.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Prakash Prasad <prakash_prasad@xxxxxxxxx>
• LVM2 volume not recognised on cold restart
  • From: Rihad <grihad@xxxxxxxxx>
• Re: [PATCH]dm-mpath: fix for race condition between multipath_dtr and pg_init_done.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• [PATCH] move the 'update_multipath_strings()' function up so that mpp->mpe can be assigned in some situation
  • From: Xinghai Yu <yuxinghai@xxxxxxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• [PATCH 2/2] dm-crypt: Add TCW IV mode for old CBC TCRYPT containers.
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH 1/2] dm-crypt: Properly handle extra key string in initialization
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• LVM2 volume not recognised on cold restart
  • From: rihad <rihad@xxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [RFC PATCH v2] dm mpath: add a queue_if_no_path timeout
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 0/2] patches to improve cluster raid1 performance [V2]
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: [PATCH] block: properly stack underlying max_segment_size to DM device
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] block: properly stack underlying max_segment_size to DM device
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-writeboost: unusual refcount on Raspberry Pi
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH]dm-mpath: fix for race condition between multipath_dtr and pg_init_done.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: [PATCH]dm-mpath: fix for race condition between multipath_dtr and pg_init_done.
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: [PATCH]dm-mpath: fix for race condition between multipath_dtr and pg_init_done.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [GIT PULL] Immutable biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 0/4] Fix error paths on device initialization in the block layer
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 4/4] bdi: test bdi_init failure
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 3/4] block: fix a probe argument to blk_register_region
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 2/4] loop: fix crash if blk_alloc_queue fails
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 1/4] blk-core: Fix memory corruption if blkcg_init_queue fails
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 0/2] patches to improve cluster raid1 performance [V2]
  • From: Dongmao Zhang <dmzhang@xxxxxxxx>
• [PATCH 3/4] block: fix a probe argument to blk_register_region
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/4] bdi: test bdi_init failure
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/4] blk-core: Fix memory corruption if blkcg_init_queue fails
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/4] loop: fix crash if blk_alloc_queue fails
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 0/4] Fix error paths on device initialization in the block layer
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH][RESEND]multipath: Allow whitespace before or after exit and quit command in multipathd
  • From: Zheng Huai Cheng <zhenghch@xxxxxxxxxxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 0/2] patches to improve cluster raid1 performance [V2]
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 0/2] patches to improve cluster raid1 performance [V2]
  • From: "Dong Mao Zhang" <dmzhang@xxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: A review of dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm-writeboost testing
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• A review of dm-writeboost
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-writeboost testing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm-writeboost testing
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writeboost testing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-writeboost testing
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: thin_dump cannot dump the correct data mapping of thin pools
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-writeboost testing
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: thin_dump cannot dump the correct data mapping of thin pools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writeboost testing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [RFC] dm-writeboost: Persistent memory support
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• thin_dump cannot dump the correct data mapping of thin pools
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• Re: dm-writeboost testing
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: dm-writeboost testing
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• dm-writeboost testing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-cache: return -EINVAL, not -ENOMEM, if the user specifies unknown policy
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-mpath: requeue I/O during pg_init
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] dm: allocate buffer for messages with small number of arguments with GFP_NOIO (resend)
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] dm: allocate buffer for messages with small number of arguments with GFP_NOIO (resend)
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm: allocate buffer for messages with small number of arguments with GFP_NOIO
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] dm: allocate buffer for messages with small number of arguments with GFP_NOIO
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/2] patches to improve cluster raid1 performance [V2]
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Holding both virtual and physical blocks prison when processing discard in dm-thin
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• [RHEL6.4] dm and multipath performance overhead
  • From: Lukasz Flis <l.flis@xxxxxxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Fwd: multipath errors
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: "Saxena, Sumit" <Sumit.Saxena@xxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Douglas Gilbert <dgilbert@xxxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Douglas Gilbert <dgilbert@xxxxxxxxxxxx>
• xfstests "free active" issue on x86?
  • From: "Michael L. Semon" <mlsemon35@xxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Douglas Gilbert <dgilbert@xxxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 0/2] patches to improve cluster raid1 performance [V2]
  • From: Dongmao Zhang <dmzhang@xxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH 1/1] dm mpath: Add timeout mechanism for queue_if_no_path.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Tuning suggestions for large systems with many (6000+) paths
  • From: Jeff Wasilko <jwasilko@xxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: RFC for multipath queue_if_no_path timeout.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH 0/2] patches to improve cluster raid1 performance [V2]
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• RFC for multipath queue_if_no_path timeout.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• [PATCH 1/2] improve the performance of dm-log-userspace
  • From: dongmao zhang <dmzhang@xxxxxxxx>
• [PATCH 2/2] change API of dm-log-userspace to support delay flush
  • From: dongmao zhang <dmzhang@xxxxxxxx>
• [PATCH 0/2] patches to improve cluster raid1 performance [V2]
  • From: dongmao zhang <dmzhang@xxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Unable to receive overwrite BIO in dm-thin
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Jeremy Linton <jlinton@xxxxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Douglas Gilbert <dgilbert@xxxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Hannes Reinecke <hare@xxxxxxx>
• [git pull] device mapper fixes for 3.12
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Ewan Milne <emilne@xxxxxxxxxx>
• Unable to receive overwrite BIO in dm-thin
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• busy paths
  • From: John Williams <john.williams.sc7@xxxxxxxxx>
• Fwd: multipath errors
  • From: Amitai Alkalay <amitai.alkalay.work@xxxxxxxxx>
• Re: linux-3.10.12 dies after many allocation errors when copying lots of data to it over nfs. How to debug?
  • From: Jan Kara <jack@xxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Douglas Gilbert <dgilbert@xxxxxxxxxxxx>
• [PATCH]multipath: Allow whitespace before or after exit and quit command in multipathd
  • From: Zheng Huai Cheng <zhenghch@xxxxxxxxxxxxxxxxxx>
• Reworking dm-writeboost [was: Re: staging: Add dm-writeboost]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] block: Add nr_bios to block_rq_remap tracepoint
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm thin: do not expose non-zero discard limits if discards are disabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm mpath: disable WRITE SAME if it fails
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• linux-3.10.12 dies after many allocation errors when copying lots of data to it over nfs. How to debug?
  • From: Stevie Trujillo <stevie.trujillo@xxxxxxxxx>
• [PATCH] dm-snapshot: fix performance degradation due to small hash size (was: [lvm-devel] Snapshotted device gets slow)
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-snapshot: workaround for a lockdep warning
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-snapshot: workaround for a lockdep warning
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [PATCH] dm-snapshot: workaround for a lockdep warning
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/7] dm: add reserved_bio_based_ios module parameter
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: [PATCH v3 0/3] dm: allow mempool and bioset reserves to be tuned
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: [PATCH] dm-snapshot: workaround for a lockdep warning
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: [PATCH] dm-snapshot: workaround for a lockdep warning
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-snapshot: workaround for a lockdep warning
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: staging: Add dm-writeboost
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-snapshot: workaround for a lockdep warning
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: staging: Add dm-writeboost
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: staging: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: staging: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [PATCH] block: Add nr_bios to block_rq_remap tracepoint
  • From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
• Re: staging: Add dm-writeboost
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: staging: Add dm-writeboost
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] remove device on close
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: ANNOUNCE: remove device on close
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• ANNOUNCE: remove device on close
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [RFC] dm-writeboost: Plan to add comments. Needs help to make an objective list of where to comment
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] dm-writeboost: Porting daemon modulating migration from userland into the kernel
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] dm-writeboost: Porting daemon modulating migration from userland into the kernel
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [RFC] dm-writeboost: Porting daemon modulating migration from userland into the kernel
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] dm-writeboost: Porting daemon modulating migration from userland into the kernel
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [RFC] dm-writeboost: Porting daemon modulating migration from userland into the kernel
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [3.10.7] Reproductible soft lockup, recover but freeze even the mouse
  • From: roucaries.bastien@xxxxxxxxx
• Re: [3.10.7] Reproductible soft lockup, recover but freeze even the mouse
  • From: Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx>
• [PATCH] dm-statistics: fix a possible counter corruption on 32-bit systems
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v3 1/3] dm: lower bio-based mempool reservation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 3/3] dm: add reserved_bio_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 2/3] dm: add reserved_rq_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 0/3] dm: allow mempool and bioset reserves to be tuned
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 0/3] dm: allow mempool and bioset reserves to be tuned
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 0/3] dm: allow mempool and bioset reserves to be tuned
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2 3/3] dm: add reserved_bio_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2 2/3] dm: add reserved_rq_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2 1/3] dm: lower bio-based mempool reservation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2 0/3] dm: allow mempool and bioset reserves to be tuned
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 5/7] dm mpath: use dm_get_reserved_rq_based_ios to size mempool
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 4/7] dm io: use dm_get_reserved_bio_based_ios to size reserves
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/7] dm: add reserved_bio_based_ios module parameter
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 6/7] dm: track the maximum number of bios in a cloned request
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/7] dm: add reserved_rq_based_ios module parameter
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 7/7] dm: optimize clone_rq() when track_peak_rq_based_ios is disabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm: add reserved_bio_based_ios module parameter
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 7/7] dm: optimize clone_rq() when track_peak_rq_based_ios is disabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 7/7] dm: optimize clone_rq() when track_peak_rq_based_ios is disabled
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/7] dm: lower bio-based mempool reservation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 7/7] dm: optimize clone_rq() when track_peak_rq_based_ios is disabled
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 7/7] dm: optimize clone_rq() when track_peak_rq_based_ios is disabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm mpath: do not fail path on -ENOSPC
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] dm mpath: do not fail path on -ENOSPC
  • From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 7/7] dm: optimize clone_rq() when track_peak_rq_based_ios is disabled
  • From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 7/7] dm: optimize clone_rq() when track_peak_rq_based_ios is disabled
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/7] dm: add reserved_rq_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 7/7] dm: optimize clone_rq() when track_peak_rq_based_ios is disabled
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/7] dm: add reserved_rq_based_ios module parameter
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/7] dm: add reserved_rq_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm: add reserved_bio_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 6/7] dm: track the maximum number of bios in a cloned request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/7] dm: lower bio-based mempool reservation
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/7] dm: track the maximum number of bios in a cloned request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 5/7] dm mpath: use dm_get_reserved_rq_based_ios to size mempool
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 4/7] dm io: use dm_get_reserved_bio_based_ios to size reserves
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 3/7] dm: add reserved_bio_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/7] dm: add reserved_rq_based_ios module parameter
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/7] dm: allow mempool and bioset reserves to be tuned
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-crypt parallelization patches
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-crypt parallelization patches
  • From: Andi Kleen <ak@xxxxxxxxxxxxxxx>
• Re: dm-crypt parallelization patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [git pull] device-mapper changes for 3.12
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• multipath errors
  • From: Amitai Alkalay <amitai.alkalay.work@xxxxxxxxx>
• [PATCH 1/1] improve the performance of dm-log-userspace
  • From: dongmao zhang <dmzhang@xxxxxxxx>
• [PATCH 0/1] ideas to improve the write performance of cluster dm-raid1
  • From: dongmao zhang <dmzhang@xxxxxxxx>
• Re: [3.10.7] Reproductible soft lockup, recover but freeze even the mouse
  • From: Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx>
• Fwd: [3.10.7] Reproductible soft lockup, recover but freeze even the mouse
  • From: Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx>
• Re: Bug 999761 - Review NetApp path_checker and features for RHEL5 mpath
  • From: Jamie Bainbridge <jbainbri@xxxxxxxxxx>
• Re: [PATCH 1/2] Revert "Revert "math64: New div64_u64_rem helper""
  • From: Anatol Pomozov <anatol.pomozov@xxxxxxxxx>
• Re: multipath 4k partition block issues.
  • From: Ross Anderson <rosander@xxxxxxxxx>
• Re: multipath 4k partition block issues.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• multipath 4k partition block issues.
  • From: Ross Anderson <rosander@xxxxxxxxx>
• Re: [PATCH 1/2] Revert "Revert "math64: New div64_u64_rem helper""
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-crypt parallelization patches
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-crypt parallelization patches
  • From: Andi Kleen <ak@xxxxxxxxxxxxxxx>
• dm-crypt parallelization patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Bug 999761 - Review NetApp path_checker and features for RHEL5 mpath
  • From: Martin George <marting@xxxxxxxxxx>
• Bug 999761 - Review NetApp path_checker and features for RHEL5 mpath
  • From: Jamie Bainbridge <jbainbri@xxxxxxxxxx>
• Re: [PATCH] dm: Deal with merge_bvec_fn in component devices better
  • From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
• Re: [PATCH] dm: Deal with merge_bvec_fn in component devices better
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm: Deal with merge_bvec_fn in component devices better
  • From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
• [PATCH] staging: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] dm-writeboost: plan to go to staging
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] dm-writeboost: plan to go to staging
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] dm-lc: plan to go to staging
  • From: Valdis.Kletnieks@xxxxxx
• Re: [RFC] dm-lc: plan to go to staging
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] dm-lc: plan to go to staging
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [RFC] dm-lc: plan to go to staging
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 3/3] dm: allow error target to replace immutable target
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/3] dm: allow error target to replace immutable target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm ioctl: prevent rename to empty name or uuid
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/3] dm: allow error target to replace immutable target
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• dm ioctl: prevent rename to empty name or uuid
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [RFC] dm-lc: plan to go to staging
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/3] dm: allow error target to replace immutable target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/3] dm: allow error target to replace immutable target
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [RFC] dm-lc: plan to go to staging
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH 3/3] dm: allow error target to replace immutable target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/3] dm ioctl: cleanup error handling in table_load
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/3] dm ioctl: increase granularity of type_lock when loading table
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC] dm-lc: plan to go to staging
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [RFC] dm-lc: plan to go to staging
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Strange mapped block count kept by dm-thin driver for thin devices
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Chaitra Bhat <Chaitra.Bhat@xxxxxxxxxxxx>
• Strange mapped block count kept by dm-thin driver for thin devices
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• Re: Status dm-cache
  • From: Rolf Fokkens <rolf@xxxxxxxxxxxxxx>
• Re: Status dm-cache
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• dm-lc: update
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Status dm-cache
  • From: Rolf Fokkens <rolf@xxxxxxxxxxxxxx>
• Re: Allow read IO during share block breaking in dm-thin
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm: allow error target to replace either bio-based and request-based targets
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Allow read IO during share block breaking in dm-thin
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] dm: allow error target to replace either bio-based and request-based targets
  • From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
• Allow read IO during share block breaking in dm-thin
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• Re: [PATCH] dm: allow error target to replace either bio-based and request-based targets
  • From: Joe Jin <joe.jin@xxxxxxxxxx>
• [PATCH] dm: allow error target to replace either bio-based and request-based targets
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm ioctl: allow change device target type to error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm ioctl: allow change device target type to error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] dm ioctl: allow change device target type to error
  • From: Joe Jin <joe.jin@xxxxxxxxxx>
• Re: [PATCH v2] dm ioctl: allow change device target type to error
  • From: Joe Jin <joe.jin@xxxxxxxxxx>
• [PATCH] math64: New separate div64_u64_rem helper
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm ioctl: allow change device target type to error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm ioctl: allow change device target type to error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v2] dm ioctl: allow change device target type to error
  • From: Joe Jin <joe.jin@xxxxxxxxxx>
• [PATCH] dm ioctl: allow change device target type to error
  • From: Joe Jin <joe.jin@xxxxxxxxxx>
• Re: [PATCH 1/2] Revert "Revert "math64: New div64_u64_rem helper""
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH] bcache: Remove use of down/up_read_non_owner()
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2] Revert "Revert "math64: New div64_u64_rem helper""
  • From: Stanislaw Gruszka <sgruszka@xxxxxxxxxx>
• Re: [PATCH 1/2] Revert "Revert "math64: New div64_u64_rem helper""
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH] bcache: Remove use of down/up_read_non_owner()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] bcache: Remove use of down/up_read_non_owner()
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] bcache: Remove use of down/up_read_non_owner()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: [PATCH] dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: [PATCH] dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [git pull] device-mapper fix for 3.11
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] Revert "Revert "math64: New div64_u64_rem helper""
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] bcache: Remove use of down/up_read_non_owner()
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH][RESEND] scsi_dh_rdac:Log batched lun information with mode select command
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] multipath: rport tmo cleanup
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: please fetch new git-based DM 'for-next' branch [was: Re: [git pull] device-mapper changes for 3.11]
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] dm cache: Avoid conflicting remove_mapping() in mq policy
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [PATCH] dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] multipath: rport tmo cleanup
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxx>
• [PATCH] dm: Make MIN_IOS, et al, tunable via sysctl.
  • From: Frank Mayhar <fmayhar@xxxxxxxxxx>
• please fetch new git-based DM 'for-next' branch [was: Re: [git pull] device-mapper changes for 3.11]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm cache: Avoid conflicting remove_mapping() in mq policy
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] dm: fix stacking of geometry limits for thinp and cache
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH] dm: fix stacking of geometry limits for thinp and cache
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Chaitra Bhat <Chaitra.Bhat@xxxxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed L Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH v2] Add log-structured caching target
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Chaitra Bhat <Chaitra.Bhat@xxxxxxxxxxxx>
• Re: noob usage question
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• [PATCH] bugfix: map_context->ptr must be nullify in no-cache path.
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [PATCH] [RFC] Implements log-structured caching target
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH 18/22] block: Generic bio chaining
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: noob usage question
  • From: John Strange <johnstra10@xxxxxxxxx>
• Re: [Question] How to make a patch?
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [Question] How to make a patch?
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [Question] How to make a patch?
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [Question] How to make a patch?
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [Question] How to make a patch?
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: noob usage question
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• noob usage question
  • From: John Strange <johnstra10@xxxxxxxxx>
• [PATCH 2/2 v3] dm: add statistics support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/2] Revert "Revert "math64: New div64_u64_rem helper""
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Extending DM w/ new target type
  • From: John Strange <johnstra10@xxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH v2] dm: add statistics support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH] rdac: Always fail paths when controller reports unavailable AAS
  • From: "Stewart, Sean" <Sean.Stewart@xxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Chaitra Bhat <Chaitra.Bhat@xxxxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Chaitra Bhat <Chaitra.Bhat@xxxxxxxxxxxx>
• Re: dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• dm-verity: Verification fails but do not see Input/Output Error on read
  • From: Chaitra Bhat <Chaitra.Bhat@xxxxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• [PATCH 09/10] idr: Remove unneeded idr locking, idr_preload() usage
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 22/22] block: Don't save/copy bvec array anymore, share when cloning
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 17/22] block: Remove bi_idx hacks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 05/22] dm: Use bvec_iter for dm_bio_record()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 03/22] bcache: Kill unaligned bvec hack
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 11/22] block: Kill bio_segments()/bi_vcnt usage
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 21/22] block: Kill bio_pair_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 13/22] ceph: Convert to immutable biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 08/22] block: Immutable bio vecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 10/22] bio-integrity: Convert to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 06/22] block: Convert bio_iovec() to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 09/22] block: Convert bio_copy_data() to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 01/22] block: Use rw_copy_check_uvector()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 02/22] block: Consolidate duplicated bio_trim() implementations
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 07/10] idr: Rename idr_alloc() -> idr_alloc_range()
  • From: Wolfram Sang <wsa@xxxxxxxxxxxxx>
• [PATCH 07/22] block: Convert bio_for_each_segment() to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 07/10] idr: Rename idr_alloc() -> idr_alloc_range()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 12/22] block: Convert drivers to immutable biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 18/22] block: Generic bio chaining
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 14/22] block: Kill bio_iovec_idx(), __bio_iovec()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 20/22] block: Introduce new bio_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 15/22] rbd: Refactor bio cloning, don't clone biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 19/22] block: Rename bio_split() -> bio_pair_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• dm-lc: updates
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm-thin - issue about the maximum size of the metadata device
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• [PATCH] scsi_dh_rdac:Log batched lun information with mode select command
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• dm-thin - issue about the maximum size of the metadata device
  • From: 梁文彥 <burton.paramountcy@xxxxxxxxx>
• dm-lc: new doc
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• dm-lc: new doc
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Fwd: Re: dm-cache with zero hit rate
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: dm-cache with zero hit rate
  • From: Amy Rupp <amymoseleyrupp@xxxxxxxxx>
• Re: dm-cache with zero hit rate
  • From: "Steinar H. Gunderson" <sgunderson@xxxxxxxxxxx>
• Re: dm-cache with zero hit rate
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Extending DM w/ new target type
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: dm-cache with zero hit rate
  • From: "Steinar H. Gunderson" <sgunderson@xxxxxxxxxxx>
• Re: state we don't understand
  • From: Amy Rupp <amymoseleyrupp@xxxxxxxxx>
• state we don't understand
  • From: Brian Bunker <brian@xxxxxxxxxxxxxxx>
• Re: Extending DM w/ new target type
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Extending DM w/ new target type
  • From: John Strange <johnstra10@xxxxxxxxx>
• Re: dm-lc code/design [was: Re: dm-lc.c: fix for a potential NULL pointer dereference]
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm-cache with zero hit rate
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-cache with zero hit rate
  • From: "Steinar H. Gunderson" <sgunderson@xxxxxxxxxxx>
• dm-lc code/design [was: Re: dm-lc.c: fix for a potential NULL pointer dereference]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-lc.c: fix for a potential NULL pointer dereference
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [PATCH] dm-lc.c: fix for a potential NULL pointer dereference
  • From: Kumar Amit Mehta <gmate.amit@xxxxxxxxx>
• Re: [PATCH v2] dm-lc.c: Audit return values of functions invoked in module init routine
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [PATCH v2] dm-lc.c: Audit return values of functions invoked in module init routine
  • From: Kumar Amit Mehta <gmate.amit@xxxxxxxxx>
• Re: [PATCH] dm-lc.c: Audit return values of functions invoked in module init routine
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: [PATCH] dm-lc.c: Audit return values of functions invoked in module init routine
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [PATCH] dm-lc.c: Audit return values of functions invoked in module init routine
  • From: Kumar Amit Mehta <gmate.amit@xxxxxxxxx>
• Re: [PATCH] dm-lc.c: return -ENOMEM if alloc_workqueue fails
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC] dm-lc target
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• [PATCH 2/9] dm: WQ_NON_REENTRANT is meaningless and going away
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: dm cache: verify metadata device is exclussive
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-lc.c: return -ENOMEM if alloc_workqueue fails
  • From: Kumar Amit Mehta <gmate.amit@xxxxxxxxx>
• Re: [RFC] dm-lc target
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-cache warming
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-cache warming
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [RFC] dm-lc target
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• dm-cache warming
  • From: Dave Pitts <dpitts@xxxxxxxx>
• Re: dm-cache: dirty state of blocks in writethrough mode
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: dm-cache: dirty state of blocks in writethrough mode
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• [PATCH] dm cache: Avoid conflicting remove_mapping() in mq policy
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• [PATCH] multipath: rport tmo cleanup
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: dm-cache: dirty state of blocks in writethrough mode
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: Substantial performance difference when reading/writing to device-mapper vs. the individual device
  • From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
• [PATCH] scsi_dh_rdac:Log batched lun information with mode select command
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• [PATCH] dm cache: verify metadata device is exclussive
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-cache: dirty state of blocks in writethrough mode
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: dm-cache: dirty state of blocks in writethrough mode
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: dm-cache: dirty state of blocks in writethrough mode
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: Substantial performance difference when reading/writing to device-mapper vs. the individual device
  • From: Kaul <mykaul@xxxxxxxxx>
• Re: [PATCH] dm-thin: Add data block size limits to the Documentation
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH] dm-thin: Add data block size limits to the Documentation
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• [PATCH] dm-thin: Add data block size limits to the Documentation
  • From: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
• Re: dm-cache: dirty state of blocks in writethrough mode
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• dm-cache: dirty state of blocks in writethrough mode
  • From: "Vijarnia, Anil" <Anil.Vijarnia@xxxxxxxxxx>
• Re: pseudo block device as metadata and cache device
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Device mapping without using initramfs
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-cache: can the same cache be used with multiple origin devices?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Substantial performance difference when reading/writing to device-mapper vs. the individual device
  • From: Kaul <mykaul@xxxxxxxxx>
• Device mapping without using initramfs
  • From: ebelcrom ebelcrom <ebelcrom@xxxxxxxxxxxxxx>
• Re: [PATCH 04/30] multipath: Increase dev_loss_tmo prior to fast_io_fail
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 04/30] multipath: Increase dev_loss_tmo prior to fast_io_fail
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• Re: [PATCH] [RESEND] hwtable: Add vendor ID and update defaults for NetApp E-Series storage
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxx>
• pseudo block device as metadata and cache device
  • From: Vivek Subbarao <vskerneldevel@xxxxxxxxx>
• Re: [PATCH] [RESEND] hwtable: Add vendor ID and update defaults for NetApp E-Series storage
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 18/30] Update multipath.conf.defaults
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 00/30] SLES resync, second try
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxx>
• Re: [PATCH 00/29] SLES resync
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• [PATCH 22/30] multipath: Implement 'property' blacklist
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 27/30] Specify checker_timeout in seconds
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 00/30] SLES resync, second try
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 10/30] kpartx: support disk with non-512B sectors
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 15/30] multipath.conf.annotated: Document rr_min_io_rq
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 11/30] multipath: Add 'Datacore Virtual Disk' to internal hardware table
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 21/30] multipath.conf.annotated: remove 'udev_dir'
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 14/30] Read directly from sysfs when checking the device size
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 29/30] multipath: reset queue_if_no_path if flush failed
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 26/30] multipathd: increase stacksize for uevent listener
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 23/30] Do not print error when rport is blocked
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 28/30] multipath: fix setting of fast_io_fail_tmo
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 09/30] multipath: Deprecate 'getuid' configuration variable
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 04/30] multipath: Increase dev_loss_tmo prior to fast_io_fail
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 18/30] Update multipath.conf.defaults
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 01/30] multipath: bind lifetime of udev context to main thread
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 06/30] libmultipath: Implement PATH_TIMEOUT
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 02/30] Document 'infinity' as possible value for dev_loss_tmo
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 05/30] libmultipath: return PATH_DOWN for quiesced paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 17/30] Correctly set max_fds in case of failure
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 08/30] kpartx: create correct symlinks for PATH_FAILED events
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 24/30] multipath: reference the udev context when starting event queue
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 19/30] Correctly set pgfailback
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 13/30] Check return value from pathinfo()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 16/30] Correctly print out 'max' for max_fds
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 12/30] Minor fixes for priority handling
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 30/30] libmultipath: read path state directly from sysfs
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 20/30] multipath.conf.5: clarify 'no_path_retry' default setting
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 25/30] multipathd: valgrind fixes
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 07/30] Deprecate pg_timeout
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 03/30] alua: Do not add preferred path priority for active/optimized
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 00/29] SLES resync
  • From: Hannes Reinecke <hare@xxxxxxx>
• [RFC] dm-lc target
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Linux Plumbers IO & File System Micro-conference
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• Re: dm-cache: can the same cache be used with multiple origin devices?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-cache: can the same cache be used with multiple origin devices?
  • From: "Mears, Morgan" <Morgan.Mears@xxxxxxxxxx>
• Re: [PATCH 00/29] SLES resync
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 00/29] SLES resync
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• [PATCH 11/29] multipath: Add 'Datacore Virtual Disk' to internal hardware table
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 00/29] SLES resync
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 19/29] Correctly set pgfailback
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 04/29] multipath: Increase dev_loss_tmo prior to fast_io_fail
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 06/29] libmultipath: Implement PATH_TIMEOUT
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 25/29] multipathd: valgrind fixes
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 23/29] Do not print error when rport is blocked
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 26/29] multipathd: increase stacksize for uevent listener
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 18/29] Update multipath.conf.defaults
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 28/29] multipath: fix setting of fast_io_fail_tmo
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 10/29] kpartx: support disk with non-512B sectors
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 22/29] multipath: Implement 'property' blacklist
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 07/29] Deprecate pg_timeout
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 24/29] multipath: reference the udev context when starting event queue
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 17/29] Correctly set max_fds in case of failure
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 16/29] Correctly print out 'max' for max_fds
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 27/29] Specify checker_timeout in seconds
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 13/29] Check return value from pathinfo()
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 15/29] multipath.conf.annotated: Document rr_min_io_rq
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 05/29] libmultipath: return PATH_DOWN for quiesced paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 12/29] Minor fixes for priority handling
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 20/29] multipath.conf.5: clarify 'no_path_retry' default setting
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 21/29] multipath.conf.annotated: remove 'udev_dir'
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 09/29] multipath: Deprecate 'getuid' configuration variable
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 03/29] alua: Do not add preferred path priority for active/optimized
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 29/29] multipath: reset queue_if_no_path if flush failed
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 14/29] Read directly from sysfs when checking the device size
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 08/29] kpartx: create correct symlinks for PATH_FAILED events
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 01/29] multipath: bind lifetime of udev context to main thread
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 02/29] Document 'infinity' as possible value for dev_loss_tmo
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: Linux Plumbers IO & File System Micro-conference
  • From: "faibish, sorin" <faibish_sorin@xxxxxxx>
• Linux Plumbers IO & File System Micro-conference
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• Re: [git pull] device-mapper changes for 3.11
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [git pull] device-mapper changes for 3.11
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [git pull] device-mapper changes for 3.11
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [git pull] device-mapper changes for 3.11
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Info on bytes flow during polling
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: [git pull] device-mapper changes for 3.11
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [git pull] device-mapper changes for 3.11
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Multipath not balancing I/O across paths evenly.
  • From: Devin <delldudedevin@xxxxxxxxx>
• about cross compile for device mapper
  • From: "=?gb18030?b?sLI=?=" <koan_002@xxxxxx>
• Re: test needed for a dm-bufio patch
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: dm-devel@xxxxxxxxxx is a list
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: dm-devel@xxxxxxxxxx is a list
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: dm-devel@xxxxxxxxxx is a list
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: dm: make alloc error info more clearly.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 07/10] idr: Rename idr_alloc() -> idr_alloc_range()
  • From: Dan Williams <djbw@xxxxxx>
• [PATCH 07/10] idr: Rename idr_alloc() -> idr_alloc_range()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 09/10] idr: Remove unneeded idr locking, idr_preload() usage
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] dm: make alloc error info more clearly.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• Re: [PATCH] dm: make alloc error info more clearly.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [PATCH] dm: make alloc error info more clearly.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• ANNOUNCE: new dm statistics patches
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] MAINTAINERS: dm-devel@xxxxxxxxxx is a list
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• Re: Performance Comparison among EnhanceIO, bcache and dm-cache.
  • From: OS Engineering <osengineering@xxxxxxxxxxxx>
• test needed for a dm-bufio patch
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-thin btree and incremental backup issue
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• Re: dm-thin btree and incremental backup issue
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH 4/4] scsi: Return ENODATA on medium error
  • From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
• dm-thin btree and incremental backup issue
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• Re: Max length limitation with BLKZEROOUT on dm device ?
  • From: Bharata B Rao <bharata.rao@xxxxxxxxx>
• Re: Max length limitation with BLKZEROOUT on dm device ?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 4/5] scsi: Return ENODATA on medium error
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 4/5] scsi: Return ENODATA on medium error
  • From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
• Max length limitation with BLKZEROOUT on dm device ?
  • From: Bharata B Rao <bharata.rao@xxxxxxxxx>
• Re: [PATCH 10/26] block: Convert drivers to immutable biovecs
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• [PATCH 4/8] Turn off user_friendly_names for netapp devices
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 8/8] fix mutipath -W on empty wwids file
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
• [PATCH 1/8] Add multipath path format wildcard
  • From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>