Linux Device-Mapper Development

• Thread Index

• [PATCH 59/78] Revert to ACT_RELOAD in domap if the map exists
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 04/78] Double uevent stacksize yet again
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 36/78] Use poll() when receiving uevents
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 48/78] multipathd: reload map if reinstate failed
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 61/78] Ignore devices when sysfs_get_tgt_nodename fails
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 39/78] multipath: Use standard 'major' macro
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 45/78] Return error when receiving CLI packet
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 19/78] multipathd: implement 'list path <path>' cli command
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 09/78] Add multipath rules for systemd support
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 49/78] multipathd: do not remove paths without uevents
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 14/78] kpartx.rules: do not call blkid
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 22/78] multipath: implement option '-u' for uevents
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 67/78] libmultipath: Fall back to SG_IO if no UID could be assigned
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 26/78] 11-dm-mpath.rules: Import blkid values if all paths are down
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 13/78] Do not print empty device strings during discovery
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 16/78] Fixup wwid blacklist printing
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 12/78] multipathd: set correct PID when running in debug mode
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 17/78] Allow for empty path argument when printing information
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 25/78] multipath.rules: fixup race condition with systemd
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 30/78] Update hwtable for EMC XtremIO
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 23/78] Install multipath rule under '56-multipath.rules'
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 08/78] Make systemd installation path configurable
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 24/78] multipath.rules: Whitelist devices
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 70/78] multipathd: use SG_IO as fallback to generate uid
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 41/78] Add paths with a size of '0' as 'ghost' paths
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 38/78] kpartx: use standard 'major' and 'minor' macros
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] dm log userspace: base: fix compile warning
  • From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
• [PATCH] dm log userspace: transfer: match wait_for_completion_timeout return type
  • From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
• Re: [PATCH 0/3][RESEND] resending find_multipaths patches
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 0/3][RESEND] resending find_multipaths patches
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH 0/3][RESEND] resending find_multipaths patches
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 2/3] libmultipath: only add uninitialized paths in check_path
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 3/3] Add find_multipaths to multipath.conf man page
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/3] add find_multipaths option
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 0/7] dm: add full blk-mq support to request-based DM
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] Update ETERNUS DX entry
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• [PATCH 2/7 v3] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/7 v3] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/7] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/7 v2] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 1/7 v2] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH 2/7] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• [PATCH 2/7 v2] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/7 v2] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/7] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/7] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• [PATCH 6/7] dm: optimize dm_mq_queue_rq to _not_ use kthread if using pure blk-mq
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 7/7] dm: add 'use_blk_mq' module param and expose in per-device ro sysfs attr
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 5/7] dm: add full blk-mq support to request-based DM
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 4/7] blk-mq: don't wait in blk_mq_queue_enter() if __GFP_WAIT isn't set
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/7] dm: add full blk-mq support to request-based DM
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 3/7] blk-mq: export blk_mq_run_hw_queues
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/7] blk-mq: add blk_mq_init_allocated_queue and export blk_mq_register_disk
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/7] blk-mq: fix use of incorrect goto label in blk_mq_init_queue error path
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm log userspace: use mempool_create_kmalloc_pool()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: konstantin <kkv@xxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Mikko Rapeli <mikko.rapeli@xxxxxx>
• Re: raid1 round-robin scheduler
  • From: konstantin <kkv@xxxxxxxx>
• Re: [PATCH 00/15] Multipath patch resync
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: konstantin <kkv@xxxxxxxx>
• [PATCH] Update ETERNUS DX entry
  • From: Gerhard Wichert <Gerhard.Wichert@xxxxxxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH] Update ETERNUS DX entry
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 10/15] multipath: blacklist virtio-blk devices
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Junichi Nomura <j-nomura@xxxxxxxxxxxxx>
• Re: [PATCH 11/15] multipath: enable configuration directory
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH 11/15] multipath: enable configuration directory
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 11/15] multipath: enable configuration directory
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: [PATCH 10/15] multipath: blacklist virtio-blk devices
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 10/15] multipath: blacklist virtio-blk devices
  • From: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx>
• Re: [PATCH 00/15] Multipath patch resync
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• [PATCH 05/15] multipathd: fix memory corruption issue
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 10/15] multipath: blacklist virtio-blk devices
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 15/15] libmultipath: autodetect ALUA CLARiiON configurations
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 02/15] libmultipath: fix sysfs_get_size bug
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 01/15] correctly set partition delimiter on rename
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 11/15] multipath: enable configuration directory
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 00/15] Multipath patch resync
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 06/15] multipathd: add deferred_remove support
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 03/15] Revert "libmultipath: fixup strlcpy"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 07/15] multipathd: don't buffer output with systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 04/15] libmultipath: refactor partmaps code
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 13/15] multipathd: Add delayed path reintegration
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 12/15] libmultipath: cleanup parser code
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 08/15] libmutipath: allow blanks in device blacklist
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 09/15] multipathd: read-only bindings
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 14/15] Fix doublee free of alias after map add failure
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [patch] dm log userspace: use mempool_create_kmalloc_pool()
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH RFC 00/10] dm-dedup: device-mapper deduplication target
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH 8/8 v2] dm: impose configurable deadline for dm_request_fn's merge heuristic
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: dm-cache metadata memory footprint
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH 2/8] dm: remove request-based DM queue's lld_busy_fn hook
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 7/8] dm sysfs: introduce ability to add writable attributes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 6/8] dm: don't start current request if it would've merged with the previous
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 3/8] dm: remove request-based logic from make_request_fn wrapper
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 8/8] dm: impose configurable deadline for dm_request_fn's merge heuristic
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 4/8] dm: only run the queue on completion if congested or no requests pending
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/8] dm: remove unnecessary wrapper around blk_lld_busy
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 5/8] dm: don't schedule delayed run of the queue if nothing to do
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/8] dm: optimize request-based queue processing
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Spelic <spelic@xxxxxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: dm-cache failure semantics in write-back mode
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: dm: impose configurable deadline for dm_request_fn's merge heuristic
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: impose configurable deadline for dm_request_fn's merge heuristic
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 2/2] dm-snapshot: suspend merging snapshot when doing exception handover
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] dm-snapshot: suspend origin when doing exception handover
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 2/2] dm-snapshot: suspend merging snapshot when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/2] dm-snapshot: suspend origin when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v2] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Laurence Oberman <loberman@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Laurence Oberman <loberman@xxxxxxxxxx>
• Re: [PATCH 0/4] dm-latency: Introduction
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/2] dm-snapshot: suspend origin when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/2] dm-snapshot: suspend merging snapshot when doing exception handover
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/4] dm-latency: add I/O latency measurement in device mapper
  • From: Coly Li <colyli@xxxxxxxxx>
• [PATCH 1/4] dm-latency: move struct mapped_device from dm.c to dm.h
  • From: Coly Li <colyli@xxxxxxxxx>
• [PATCH 4/4] dm-latency: add reset function to dm-latency in sysfs interface
  • From: Coly Li <colyli@xxxxxxxxx>
• [PATCH 3/4] dm-latency: add sysfs interface
  • From: Coly Li <colyli@xxxxxxxxx>
• [PATCH 0/4] dm-latency: Introduction
  • From: Coly Li <colyli@xxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: "Busch, Keith" <keith.busch@xxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: FIXED! [was: awful request merge results while simulating high IOPS] multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• FIXED! [was: awful request merge results while simulating high IOPS] multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: awful request merge results while simulating high IOPS multipath
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• awful request merge results while simulating high IOPS multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [RFC PATCH 4/4 v2] dm: delay running the queue slightly during request completion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 4/4] dm: delay running the queue slightly during request completion
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 3/4] dm: remove request-based logic from make_request_fn wrapper
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [RFC PATCH 4/4] dm: delay running the queue slightly during request completion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/4] dm: remove request-based DM queue's lld_busy_fn hook
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/4] dm: remove unnecessary wrapper around blk_lld_busy
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/4] dm: simplify request-based DM a bit and an RFC-like perf tweak
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [Lsf] dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [Lsf] dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [Lsf] dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: [Lsf] dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• dm-mpath request merging concerns [was: Re: It's time to put together the schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: System freeze for few seconds when using dm-cache on high load
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [git pull] additional device mapper changes for 3.20
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: Performance testing of related dm-crypt patches
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Performance testing of related dm-crypt patches
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: konstantin <kkv@xxxxxxxx>
• Re: dm-mirror: do not degrade the mirror on discard error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-mirror: do not degrade the mirror on discard error
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: dm-mirror: do not degrade the mirror on discard error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-snapshot: fix a possible invalid memory access on unload
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm: fix a race condition in dm_get_md
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• dm-cache metadata memory footprint
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• dm-cache failure semantics in write-back mode
  • From: Thanos Makatos <thanos.makatos@xxxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Mikko Rapeli <mikko.rapeli@xxxxxx>
• [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Mikko Rapeli <mikko.rapeli@xxxxxx>
• Re: [PATCH 15/45] dm-log-userspace.h: include stdint.h in userspace
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• targeting dm-crypt cpu scalability changes for 3.20 still [was: Re: [git pull] device mapper changes for 3.16]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: [PATCH 6/7] dm-crypt: make it possible to disable offload to thread
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: dm-mirror: do not degrade the mirror on discard error
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 4/7] dm-crypt: remove io_pool
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH 7/7] dm-crypt: sort writes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• [PATCH v2] dm-io: reject unsupported DISCARD requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [PATCH 3/3] md bitmap: export bitmap_destroy() to support dm-raid down takover to raid0
  • From: heinzm@xxxxxxxxxx
• [PATCH 2/3] md raid0: access mddev->queue (request queue member) conditionally because it is not set when accessed from dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH 1/3] md core: add 2 API functions for takeover and resize to support dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: heinzm@xxxxxxxxxx
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 7/7] dm-crypt: sort writes
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 6/7] dm-crypt: make it possible to disable offload to thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 5/7] dm-crypt: offload writes to thread
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 4/7] dm-crypt: remove io_pool
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3/7] dm-crypt: avoid deadlock in mempools
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATH 2/7] dm-crypt: don't allocate pages for a partial request.
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 1/7] dm-crypt: use unbound workqueue for request processing
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• [git pull] device mapper changes for 3.20
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm space map disk: fix sm_disk_count_is_more_than_one()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm log userspace: split flush_entry_pool to be per dirty-log [was: Re: mempool.c: Replace io_schedule_timeout with io_schedule]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm-mirror: do not degrade the mirror on discard error
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH v2 3/3] dm: Get devices using name_to_dev_t
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 2/3] init: Stricter checking of major:minor root= values
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 1/3] init: Export name_to_dev_t and mark it const
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 1/3] init: Export name_to_dev_t and mark it const
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• Re: [PATCH RFCv2 05/10] dm-dedup: COW B-tree backend
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH RFCv2 05/10] dm-dedup: COW B-tree backend
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH] dm: fix multipath regression due to initializing wrong request
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: [PATCH] sched: call blk_schedule_flush_plug from io_schedule
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] dm: Get devices using name_to_dev_t
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] sched: call blk_schedule_flush_plug from io_schedule
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm: fix multipath regression due to initializing wrong request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm: fix multipath regression due to initializing wrong request
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq crash with dm-multipath in for-3.20/core
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• blk-mq crash with dm-multipath in for-3.20/core
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: blk-mq crash with dm-multipath in for-3.20/core
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq crash with dm-multipath in for-3.20/core
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-cache: Promote-Demote Policy. How it works ?
  • From: "BK, GirishKumar" <GirishKumar.BK@xxxxxxxxxx>
• Re: dm-dedup can not make module
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2] block: do not merge two requests with sg gaps if unsupported
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-dedup can not make module
  • From: Zhichao Cao <caozhichao91@xxxxxxxxx>
• Re: [PATCH v2] block: do not merge two requests with sg gaps if unsupported
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFCv2 03/10] dm-dedup: hash computation
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH RFCv2 02/10] dm-dedup: core deduplication logic
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: dmcache RAID1 bug?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFCv2 02/10] dm-dedup: core deduplication logic
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH][RFC] dm: log writes target
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [PATCH][RFC] dm: log writes target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH][RFC] dm: log writes target
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] Remove might_sleep from wait_event_cmd
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH RFCv2 10/10] dm-dedup: documentation
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH] Remove might_sleep from wait_event_cmd
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] dm snapshot: Deletion of unnecessary checks before the function call "vfree"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Remove might_sleep from wait_event_cmd
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dm create error
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH RFCv2 02/10] dm-dedup: core deduplication logic
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• [PATCH] Remove might_sleep from wait_event_cmd
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md:Remove unneeded fixme comment for the function, pool_ctr
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH RFCv2 10/10] dm-dedup: documentation
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Anand Jain <Anand.Jain@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]X
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]X
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]X
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]X
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Anand Jain <Anand.Jain@xxxxxxxxxx>
• Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] last couple device mapper fixes for 3.19 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• [PATCH 1/2] init: Stricter checking of major:minor root= values
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 2/2] dm: Get devices using name_to_dev_t
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [Lsf-pc] [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Anand Jain <anand.jain@xxxxxxxxxx>
• Re: [patch] dm cache: fix up IS_ERR vs NULL confusion
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [patch] dm cache: fix up IS_ERR vs NULL confusion
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: DM-Delay
  • From: "BK, GirishKumar" <GirishKumar.BK@xxxxxxxxxx>
• [patch] dm cache: fix up IS_ERR vs NULL confusion
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: dm_mirror/dm_raid1 limitations ?.
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: NeilBrown <neilb@xxxxxxx>
• blk-mq DM changes for 3.20 [was: Re: blk-mq request allocation stalls]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm create error
  • From: Xiaoqiang Zhou <zhouxiaoqiang.mstech@xxxxxxxxx>
• Re: [Lsf-pc] [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: dm_mirror/dm_raid1 limitations ?.
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: dm_mirror/dm_raid1 limitations ?.
  • From: "suresh.babu.kandukuru@xxxxxxxxxx" <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: dm_mirror/dm_raid1 limitations ?.
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• dm_mirror/dm_raid1 limitations ?.
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• [PATCH] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <dm-devel@xxxxxxxxxxxxxxxxxx>
• [PATCH] md: fix raid5 livelock
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• [git pull] a few additional device mapper fixes for 3.19 final
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm: Respect request queue page gaps flag
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: Some thoughts about providing data block checksumming for ext4
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: dm-cache - should origin device and cache be identical when quiescent?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• A couple of questions related to dm-thin in linux-3.19-rc5
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• dm-cache - should origin device and cache be identical when quiescent?
  • From: Alex Sudakar <alex.sudakar@xxxxxxxxx>
• Re: DM-Delay
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• DM-Delay
  • From: Sourav Basu <sourav.juit@xxxxxxxxx>
• Re: livelock on MD RAID5
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: nick <xerofoify@xxxxxxxxx>
• Re: [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• livelock on MD RAID5
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH 7/8] multipathd: don't buffer output with systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 3/8] Revert "libmultipath: fixup strlcpy"
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 4/8] libmultipath: refactor partmaps code
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 2/8] libmultipath: fix sysfs_get_size bug
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 0/8] Misc multipath patches.
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 6/8] multipathd: add deferred_remove support
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 1/8] correctly set partition delimiter on rename
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 5/8] multipathd: fix memory corruption issue
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH 8/8] libmutipath: allow blanks in device blacklist
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: dm: Get devices using name_to_dev_t
  • From: Daniel Ehrenberg <dehrenberg@xxxxxxxxxx>
• Re: dm: Get devices using name_to_dev_t
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm: Get devices using name_to_dev_t
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• System freeze for few seconds when using dm-cache on high load
  • From: Michał Zubkowicz <michal.zubkowicz@xxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: [PATCH 3/6] libmultipath: add overrides section to multipath.conf
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/6] libmultipath: add overrides section to multipath.conf
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm + blk-mq soft lockup complaint
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/6] libmultipath: add overrides section to multipath.conf
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• multipath-tools-0.5.0 segfault with blacklist/blacklist_exceptions
  • From: Brian De Wolf <bldewolf@xxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• [PATCH] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• multipath-tools-0.5.0 segfault with blacklist/blacklist_exceptions
  • From: Brian De Wolf <bldewolf@xxxxxxx>
• Re: [PATCH 3/6] libmultipath: add overrides section to multipath.conf
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: blk-mq request allocation stalls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/6] libmultipath: add overrides section to multipath.conf
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH v2 1/9] block: make generic_make_request handle arbitrarily sized bios
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• [PATCH v2 7/9] block: kill merge_bvec_fn() completely
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: Device mapper target driver for Write tracking or Write split
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: Device mapper target driver for Write tracking or Write split
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• [PATCH] dm mpath: simplify failure path of dm_miltipath_init()
  • From: Johannes Thumshirn <morbidrsa@xxxxxxxxx>
• Re: [PATCH 3/6] libmultipath: add overrides section to multipath.conf
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 3/6] libmultipath: add overrides section to multipath.conf
  • From: Sebastian Herbszt <herbszt@xxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Device mapper target driver for Write tracking or Write split
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: Device mapper target driver for Write tracking or Write split
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: Device mapper target driver for Write tracking or Write split
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: Device mapper target driver for Write tracking or Write split
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: Device mapper target driver for Write tracking or Write split
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: [PATCH 2/3] libmultipath: cleanup propsel.c with macros for common actions
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• multipathd, mpathpersist and APTPL
  • From: Ken Raeburn <raeburn@xxxxxxxxxxxx>
• Device mapper target driver for Write tracking or Write split
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• [PATCH] dm: handle multiple internal suspends correctly (was: staged dm_internal_{suspend, resume} related changes for wider review)
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 3/6] libmultipath: add overrides section to multipath.conf
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH 5/6] correctly set partition delimiter on rename
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] libmultipath: Fix memory leak problem in print_multipath_topology
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [PATCH] libmultipath: Add Dell 36xxi/f support to internal hardware table
  • From: Christophe Varoqui <christophe.varoqui@xxxxxxxxxxx>
• Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] dm bufio: fix time comparison
  • From: Asaf Vertz <asaf.vertz@xxxxxxxxxxx>
• Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] Update CONFIG_DM_CRYPT help-text link
  • From: Loic Pefferkorn <loic@xxxxxxxx>
• Re: blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Jens Axboe <axboe@xxxxxxxxx>
• blk-mq request allocation stalls [was: Re: [PATCH v3 0/8] dm: add request-based blk-mq support]
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: DM limits setup
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: DM limits setup
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: staged dm_internal_{suspend, resume} related changes for wider review
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: DM limits setup
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: Questions about the function, queue_empty in dm-cache-policy-mq.c
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Questions about the function, queue_empty in dm-cache-policy-mq.c
  • From: nick <xerofoify@xxxxxxxxx>
• [LSF/MM ATTEND] discuss blk-mq related to DM-multipath and status of XCOPY
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: staged dm_internal_{suspend, resume} related changes for wider review
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 3.15-3.18] dm thin: fix a race in thin_dtr
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH v3] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [RFC PATCH 01/17] block: make generic_make_request handle arbitrarily sized bios
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: all cache blocks marked as dirty in writethrough mode, no way to avoid
  • From: Marc Lehmann <schmorp@xxxxxxxxxx>
• [PATCH] md: dm-thin-metadata: Remove unused function
  • From: Rickard Strandqvist <rickard_strandqvist@xxxxxxxxxxxxxxxxxx>
• DM limits setup
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: Hibernate/Resume and dm-cache, dm-writeboost...
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Hibernate/Resume and dm-cache, dm-writeboost...
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH] libmultipath: Fix memory leak problem in print_multipath_topology
  • From: Yingtai Xie <xieyingtai@xxxxxxxxxx>
• [PATCH] drivers:md: Remove unneeded fix me comments in dm-bio-prison.h
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [RFC PATCH 01/17] block: make generic_make_request handle arbitrarily sized bios
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Hibernate/Resume and dm-cache, dm-writeboost...
  • From: Rolf Fokkens <rolf@xxxxxxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [PATCH] dm: fix wrong comment
  • From: Junxiao Bi <junxiao.bi@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxx>
• Can get the size of original bio from split bio?
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <msnitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [RFC PATCH 01/17] block: make generic_make_request handle arbitrarily sized bios
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 01/17] block: make generic_make_request handle arbitrarily sized bios
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [git pull] device mapper fixes for 3.19
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• [RFC PATCH 14/17] block: kill merge_bvec_fn() completely
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• [RFC PATCH 01/17] block: make generic_make_request handle arbitrarily sized bios
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: mempool.c: Replace io_schedule_timeout with io_schedule
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: multipath breaks with recent udev/systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: multipath breaks with recent udev/systemd
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: multipath breaks with recent udev/systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: multipath breaks with recent udev/systemd
  • From: Kay Sievers <kay@xxxxxxxx>
• Re: mempool.c: Replace io_schedule_timeout with io_schedule
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] mempool.c: Replace io_schedule_timeout with io_schedule
  • From: Timofey Titovets <nefelim4ag@xxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm: check error instead of r in clone_endio
  • From: alex chen <alex.chen@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 8/8] dm: allocate requests from target when stacking on blk-mq devices
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm: check error instead of r in clone_endio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm thin: Initialize refcount and completion earlier
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm thin: Initialize refcount and completion earlier
  • From: Marc Dionne <marc.c.dionne@xxxxxxxxx>
• Re: multipath breaks with recent udev/systemd
  • From: Hannes Reinecke <hare@xxxxxxx>
• [PATCH] dm: check error instead of r in clone_endio
  • From: alex chen <alex.chen@xxxxxxxxxx>
• [PATCH v3 5/8] dm: remove exports for request-based interfaces without external callers
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 8/8] dm: allocate requests from target when stacking on blk-mq devices
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 4/8] block: mark blk-mq devices as stackable
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 6/8] dm: split request structure out from dm_rq_target_io structure
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 7/8] dm: submit stacked requests in irq enabled context
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 3/8] block: add blk-mq support to blk_insert_cloned_request()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 2/8] block: initialize bio member of blk-mq request to NULL
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 0/8] dm: add request-based blk-mq support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 1/8] block: require blk_rq_prep_clone() be given an initialized clone request
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: multipath breaks with recent udev/systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• Re: multipath breaks with recent udev/systemd
  • From: "Benjamin Marzinski" <bmarzins@xxxxxxxxxx>
• [PATCH] Update CONFIG_DM_CRYPT help-text link
  • From: Loic Pefferkorn <loic@xxxxxxxx>
• Re: [systemd-devel] multipath breaks with recent udev/systemd
  • From: "Alexander E. Patrakov" <patrakov@xxxxxxxxx>
• multipath breaks with recent udev/systemd
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Jianjian Huo <samuel.huo@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Jianjian Huo <samuel.huo@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Jianjian Huo <samuel.huo@xxxxxxxxx>
• Re: [PATCHv2 0/4] blk-mq support for dm multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Spelic <spelic@xxxxxxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v2] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [lvm-devel] [PATCH] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <ewheeler@xxxxxxxxxxxx>
• Re: staging: writeboost: Add dm-writeboost
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Marian Csontos <mcsontos@xxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <lvm-dev@xxxxxxxxxxxxxxxxxx>
• [PATCH][RFC] dm: log writes target
  • From: Josef Bacik <jbacik@xxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [git pull] device mapper changes for 3.19
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• [PATCH] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <lvm-dev@xxxxxxxxxxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <lvm-dev@xxxxxxxxxxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <lvm-dev@xxxxxxxxxxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <lvm-dev@xxxxxxxxxxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Eric Wheeler <lvm-dev@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCH] staging: writeboost: Add dm-writeboost
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [lvm-devel] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCHv2 0/4] blk-mq support for dm multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCHv2 0/4] blk-mq support for dm multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• dm-writeboost: An idea of adding read-caching
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: [PATCHv2 0/4] blk-mq support for dm multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCHv2 0/4] blk-mq support for dm multipath
  • From: Keith Busch <keith.busch@xxxxxxxxx>
• Re: [PATCHv2 0/4] blk-mq support for dm multipath
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Vasiliy Tolstov <v.tolstov@xxxxxxxxx>
• Re: dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Vasiliy Tolstov <v.tolstov@xxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Vasiliy Tolstov <v.tolstov@xxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: "Bryn M. Reeves" <bmr@xxxxxxxxxx>
• Re: raid1 round-robin scheduler
  • From: Vasiliy Tolstov <v.tolstov@xxxxxxxxx>
• raid1 round-robin scheduler
  • From: Vasiliy Tolstov <v.tolstov@xxxxxxxxx>
• [PATCH]libmultipath: Add default hardware table entry for IBM DCS3860 with product ID 1813.
  • From: "Merla, ShivaKrishna" <ShivaKrishna.Merla@xxxxxxxxxx>
• Re: dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm thin: optimize away writing all zeroes to unprovisioned blocks
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: [PATCH RFCv2 01/10] dm-dedup: main data structures
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: [PATCH RFCv2 00/10] dm-dedup: device-mapper deduplication target
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: dm-bufio: fix memleak when using a dm_buffer's inline bio
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-bufio: fix memleak when using a dm_buffer's inline bio
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [patch] dm space map metadata: fix sm_bootstrap_get_nr_blocks()
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH 5/8] dm: replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 0/8] replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 0/8] replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [patch] dm space map metadata: fix sm_bootstrap_get_nr_blocks()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: dm-writeboost: About inclusion into mainline
  • From: Akira Hayakawa <ruby.wktk@xxxxxxxxx>
• Re: Possible bug when releasing metadata snapshot in dm-thin
  • From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Unable to deactivate lv, pehaps due to semaphore problem...
  • From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
• Re: [PATCH RFCv2 01/10] dm-dedup: main data structures
  • From: Erez Zadok <ezk@xxxxxxxxxxxxxxxxx>
• Re: Some thoughts about providing data block checksumming for ext4
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: Some thoughts about providing data block checksumming for ext4
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Some thoughts about providing data block checksumming for ext4
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: virtio_blk: fix defaults for max_hw_sectors and max_segment_size
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: virtio_blk: fix defaults for max_hw_sectors and max_segment_size
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: virtio_blk: fix defaults for max_hw_sectors and max_segment_size
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: virtio_blk: fix defaults for max_hw_sectors and max_segment_size
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: virtio_blk: fix defaults for max_hw_sectors and max_segment_size
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: virtio_blk: fix defaults for max_hw_sectors and max_segment_size
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH RFCv2 01/10] dm-dedup: main data structures
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: dm-bufio: fix memleak when using a dm_buffer's inline bio
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH RFCv2 01/10] dm-dedup: main data structures
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH RFCv2 01/10] dm-dedup: main data structures
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writeboost: About inclusion into mainline
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>