Linux Device-Mapper Development

Thread Index

failure in path between fc switch and storage: info request
- From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
Re: unmapping luns doesn't work (good)
- From: "Chauhan, Vijay" <Vijay.Chauhan@xxxxxxx>
Re: [PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: [PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: [PATCH] dm: use revalidate_disk to update device size after set_capacity
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: i_size misuses
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: i_size misuses
- From: Neil Brown <neilb@xxxxxxx>
[PATCH] dm: use revalidate_disk to update device size after set_capacity
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: introduce dm-snap-mv
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: i_size misuses
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
dm-snap-mv update
- From: McPacino <mcpacino@xxxxxxxxx>
device mapper multipath and /sys/block/XXX/device/queue_dept
- From: "Janec, Jozef" <jozef.janec@xxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: [PATCH] scsi_dh_rdac: Add two new SUN devices to rdac_dev_list
- From: Chandra Seetharaman <sekharan@xxxxxxxxxx>
unmapping luns doesn't work (good)
- From: Rudy Gevaert <Rudy.Gevaert@xxxxxxxx>
[PATCH] Fix missing dm_put()
- From: Peter Jones <pjones@xxxxxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: Hannes Reinecke <hare@xxxxxxx>
[PATCH] scsi_dh_rdac: Add two new SUN devices to rdac_dev_list
- From: "Chauhan, Vijay" <Vijay.Chauhan@xxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: [PATCH] Make it possible to set a uuid if one was not set during DM_DEV_CREATE.
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: block: eliminate potential for infinite loop in blkdev_issue_discard
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
[PATCH 19/22] dm: use little endian bit operations
- From: Akinobu Mita <akinobu.mita@xxxxxxxxx>
Re: block: eliminate potential for infinite loop in blkdev_issue_discard
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH] Fix double free and use generic private pointer in per-cpu struct
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: introduce dm-snap-mv
- From: McPacino <mcpacino@xxxxxxxxx>
Re: raid0 and discard/trim - current state?
- From: Mike Snitzer <snitzer@xxxxxxxxx>
Re: [PATCH] device-mapper: Allow setting of UUID via rename if not already set
- From: Peter Jones <pjones@xxxxxxxxxx>
[PATCH wq#for-next] workqueue: fix HIGHPRI handling in keep_working()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
[PATCH] Fix double free and use generic private pointer in per-cpu struct
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: DM-CRYPT: Scale to multiple CPUs v3
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Re: [PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: [PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Re: [PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Re: [PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: [PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Milan Broz <mbroz@xxxxxxxxxx>
[PATCH] DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Re: [PATCH] virtio-blk: put request that was created to retrieve the device id
- From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Q: Device mapper core and private biosets
- From: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
[PATCH] device-mapper: Allow setting of UUID via rename if not already set
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: Make it possible to set a uuid if one was not set during DM_DEV_CREATE.
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH] Make it possible to set a uuid if one was not set during DM_DEV_CREATE.
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
[PATCH] Make it possible to set a uuid if one was not set during DM_DEV_CREATE.
- From: Peter Jones <pjones@xxxxxxxxxx>
Re: Linux 2.6.36-rc7
- From: Tejun Heo <tj@xxxxxxxxxx>
[2.6.36 REGRESSION] Re: virtio-blk: put request that was created to retrieve the device id
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: introduce dm-snap-mv
- From: Daniel Phillips <phillips@xxxxxxxxx>
Re: introduce dm-snap-mv
- From: McPacino <mcpacino@xxxxxxxxx>
Re: introduce dm-snap-mv
- From: Christoph Hellwig <hch@xxxxxx>
Re: introduce dm-snap-mv
- From: McPacino <mcpacino@xxxxxxxxx>
Re: introduce dm-snap-mv
- From: McPacino <mcpacino@xxxxxxxxx>
Problem regarding splitting and merging of bio's in dm target
- From: nishant mungse <nishantmungse@xxxxxxxxx>
Re: introduce dm-snap-mv
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH] Make it possible to set a uuid if one was not set during DM_DEV_CREATE.
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: introduce dm-snap-mv
- From: Daniel Phillips <phillips@xxxxxxxxx>
Re: Linux 2.6.36-rc7
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: Linux 2.6.36-rc7
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH] Make it possible to set a uuid if one was not set during DM_DEV_CREATE.
- From: Peter Jones <pjones@xxxxxxxxxx>
[PATCH] Make it possible to set a uuid if one was not set during DM_DEV_CREATE.
- From: Peter Jones <pjones@xxxxxxxxxx>
introduce dm-snap-mv
- From: Cong Meng <mcpacino@xxxxxxxxx>
Re: [Bug 19642] New: 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [Bug 19642] New: 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
- From: James Bottomley <James.Bottomley@xxxxxxx>
Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [Patch] scsi_dh_rdac: retry IO for 06/3f/03 in rdac_check_sense fn
- From: "Chauhan, Vijay" <Vijay.Chauhan@xxxxxxx>
Re: [PATCH] dm-thinp: new device mapper target to thin provision storage
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
[PATCH 1 of 1] dm log userspace add version number
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
[PATCH 1 of 2] dm log userspace split flush queue
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
[PATCH 2 of 2] dm log userspace group clear and mark requests
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
[PATCH 1 of 1] dm log userspace check additional error conditions
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: [PATCH] dm-thinp: new device mapper target to thin provision storage
- From: Phillip Susi <psusi@xxxxxxxxxx>
Re: [PATCH] dm-thinp: new device mapper target to thin provision storage
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [PATCH] dm-thinp: new device mapper target to thin provision storage
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [PATCH] dm-thinp: new device mapper target to thin provision storage
- From: Hannes Reinecke <hare@xxxxxxx>
Re: [PATCH] dm-thinp: new device mapper target to thin provision storage
- From: Phillip Susi <psusi@xxxxxxxxxx>
[PATCH] dm-thinp: new device mapper target to thin provision storage
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
[PATCH] block: eliminate potential for infinite loop in blkdev_issue_discard
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: SMP aware kcryptd
- From: Milan Broz <mbroz@xxxxxxxxxx>
SMP aware kcryptd
- From: baishakhi ray <bray.cs.colorado@xxxxxxxxx>
Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
Re: idr_get_new_exact ?
- From: Tejun Heo <htejun@xxxxxxxxx>
Re: idr_get_new_exact ?
- From: Paul Mundt <lethal@xxxxxxxxxxxx>
scsi_dh_emc vs scsi_dh_alua in RHEL5.5
- From: Brian De Wolf <bldewolf@xxxxxxxxxxxxx>
Re: [PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Malahal Naineni <malahal@xxxxxxxxxx>
[PATCH] block: set the bounce_pfn to the actual DMA limit rather than to max memory
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [PATCH] virtio-blk: put request that was created to retrieve the device id
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: Help ! : device-mapper: reload ioctl failed: Invalid argument
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Ryan Harper <ryanh@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Ryan Harper <ryanh@xxxxxxxxxx>
Re: [PATCH] virtio-blk: put request that was created to retrieve the device id
- From: Ryan Harper <ryanh@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Ryan Harper <ryanh@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Ryan Harper <ryanh@xxxxxxxxxx>
OT: device mapper development/testing.
- From: Philip Vossler <philvossler@xxxxxxxxxxxxxx>
Help ! : device-mapper: reload ioctl failed: Invalid argument
- From: Sethuraman Subbiah <ssubbia2@xxxxxxxx>
Re: idr_get_new_exact ?
- From: Steve Wise <swise@xxxxxxxxxxxxxxxxxxxxx>
Re: Is it deliberate that the device mapper is not passing the DISCARD ioctls
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: Is it deliberate that the device mapper is not passing the DISCARD ioctls
- From: Lukas Czerner <lczerner@xxxxxxxxxx>
multipath-tools ./multipath.conf.defaults libm ...
- From: bmarzins@xxxxxxxxxxxxxx
Re: idr_get_new_exact ?
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: idr_get_new_exact ?
- From: Tejun Heo <htejun@xxxxxxxxx>
Re: idr_get_new_exact ?
- From: Roland Dreier <rdreier@xxxxxxxxx>
idr_get_new_exact ?
- From: Ohad Ben-Cohen <ohad@xxxxxxxxxx>
Re: idr_get_new_exact ?
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Re: Is it deliberate that the device mapper is not passing the DISCARD ioctls
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: Is it deliberate that the device mapper is not passing the DISCARD ioctls
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Is it deliberate that the device mapper is not passing the DISCARD ioctls
- From: "Theodore Ts'o" <tytso@xxxxxxx>
[PATCH] dm: Fix possible NULL dereferences
- From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: new "multi-version snapshot target" [was: Re: [PATCH] vfs: calculate block-size correctly]
- From: McPacino <mcpacino@xxxxxxxxx>
new "multi-version snapshot target" [was: Re: [PATCH] vfs: calculate block-size correctly]
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
multipath-tools ./multipath.conf.defaults libm ...
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: Combined storage tree
- From: James Bottomley <James.Bottomley@xxxxxxx>
Re: Combined storage tree
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: i_size misuses
- From: Neil Brown <neilb@xxxxxxx>
Re: Combined storage tree
- From: James Bottomley <James.Bottomley@xxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Ric Wheeler <rwheeler@xxxxxxxxxx>
Re: Combined storage tree
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Combined storage tree
- From: James Bottomley <James.Bottomley@xxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
shared snapshots
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
multipath-tools/libmultipath dict.c
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCHSET #upstream] block, fs: replace HARDBARRIER with FLUSH/FUA, take#2
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Jan Kara <jack@xxxxxxx>
[PATCH] dm: use cpu_relax when busy waiting for condition
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH] virtio-blk: put request that was created to retrieve the device id
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
[PATCH] virtio-blk: put request that was created to retrieve the device id
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
multipath-tools libmultipath/config.h libmulti ...
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCHSET #upstream] block, fs: replace HARDBARRIER with FLUSH/FUA, take#2
- From: Tejun Heo <teheo@xxxxxxx>
Re: [PATCH 42/41 v2] dm: convey that all flushes are processed as empty
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 42/41 v2] dm: convey that all flushes are processed as empty
- From: Tejun Heo <tj@xxxxxxxxxx>
i_size misuses
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
[PATCH 42/41 v2] dm: convey that all flushes are processed as empty
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 24/41] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [PATCH 42/41] dm: convey that all flushes are processed as empty
- From: Christoph Hellwig <hch@xxxxxx>
[PATCH 42/41] dm: convey that all flushes are processed as empty
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: dm_crypt: very low performance of random IO operations
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: [PATCH 24.5/30] jbd2: Modify ASYNC_COMMIT code to not rely on queue draining on barrier
- From: Sergei Shtylyov <sshtylyov@xxxxxxxxxx>
[PATCH 04/41] block: deprecate barrier and replace blk_queue_ordered() with blk_queue_flush()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: Sergei Shtylyov <sshtylyov@xxxxxxxxxx>
Re: [PATCH 04/30] block: deprecate barrier and replace blk_queue_ordered() with blk_queue_flush()
- From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
Re: [PATCH 24.5/30] jbd2: Modify ASYNC_COMMIT code to not rely on queue draining on barrier
- From: Andreas Dilger <adilger@xxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Jamie Lokier <jamie@xxxxxxxxxxxxx>
doubt in installation of dm-ioband
- From: sethu subbiah <sethusubbiah@xxxxxxxxx>
Re: [PATCH 24.5/30] jbd2: Modify ASYNC_COMMIT code to not rely on queue draining on barrier
- From: Jan Kara <jack@xxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Milan Broz <mbroz@xxxxxxxxxx>
multipath-tools multipath.conf.annotated multi ...
- From: bmarzins@xxxxxxxxxxxxxx
multipath-tools/libmultipath config.h dict.c s ...
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCHSET #upstream] block, fs: replace HARDBARRIER with FLUSH/FUA, take#2
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
Re: [PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH 28/41] xfs: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 23/41] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 21/41] md: implment REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 16/41] block: update documentation for REQ_FLUSH / REQ_FUA
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 07/41] block: drop barrier ordering by queue draining
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCHSET #upstream] block, fs: replace HARDBARRIER with FLUSH/FUA, take#2
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 03/41] block: kill QUEUE_ORDERED_BY_TAG
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 18/41] block/loop: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 35/41] jbd2: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 14/41] block: kick queue after sequencing REQ_FLUSH/FUA
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 31/41] reiserfs: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 40/41] block: remove the BLKDEV_IFL_BARRIER flag
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 36/41] ext4: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 22/41] block: make __blk_rq_prep_clone() copy most command flags
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 09/41] block: rename barrier/ordered to flush
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 20/41] lguest: replace VIRTIO_F_BARRIER support with VIRTIO_F_FLUSH support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 32/41] nilfs2: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 25/41] dm: relax ordering of bio-based flush implementation
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 05/41] block: remove spurious uses of REQ_HARDBARRIER
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 37/41] fat: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 06/41] block: misc cleanups in barrier code
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 08/41] block: rename blk-barrier.c to blk-flush.c
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 41/41] block: remove the BH_Eopnotsupp flag
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 10/41] block: implement REQ_FLUSH/FUA based interface for FLUSH/FUA requests
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 27/41] block: pass gfp_mask and flags to sb_issue_discard
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 33/41] jbd: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 38/41] swap: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 30/41] gfs2: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 11/41] block: filter flush bio's in __generic_make_request()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 15/41] block: make sure FSEQ_DATA request has the same rq_disk as the original
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 39/41] block: remove the WRITE_BARRIER flag
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 19/41] virtio_blk: drop REQ_HARDBARRIER support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 29/41] btrfs: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 24/41] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 17/41] block: use REQ_FLUSH in blkdev_issue_flush()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 34/41] jbd2: Modify ASYNC_COMMIT code to not rely on queue draining on barrier
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 26/41] dm: fix locking context in queue_io()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 12/41] block: simplify queue_next_fseq
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 01/41] ide: remove unnecessary blk_queue_flushing() test in do_ide_request()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 02/41] block/loop: queue ordered mode should be DRAIN_FLUSH
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 13/41] block: initialize flush request with WRITE_FLUSH instead of REQ_FLUSH
- From: Tejun Heo <tj@xxxxxxxxxx>
dm_crypt: very low performance of random IO operations
- From: Yakov Hrebtov <hrebtov@xxxxxxxxx>
Re: Discard support for dm-snap
- From: Hannes Reinecke <hare@xxxxxxx>
multipath-tools ./multipath.conf.defaults libm ...
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: Discard support for dm-snap
- From: Douglas McClendon <dmc.fedora@xxxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] [PATCH] option to multipath to not modify the bindinfs file
- From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: Discard support for dm-snap
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Discard support for dm-snap
- From: Hannes Reinecke <hare@xxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
multipath-tools/multipathd main.c
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 3/5] dm: relax ordering of bio-based flush implementation
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 2/5] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 2/5] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 2/5] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 3/5] dm: relax ordering of bio-based flush implementation
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 2/5] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: safety of retrying SYNCHRONIZE CACHE [was: Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush]
- From: Hannes Reinecke <hare@xxxxxxx>
Re: safety of retrying SYNCHRONIZE CACHE [was: Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush]
- From: Hannes Reinecke <hare@xxxxxxx>
safety of retrying SYNCHRONIZE CACHE [was: Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush]
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
Re: [PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Jeff Moyer <jmoyer@xxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Jan Kara <jack@xxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Ric Wheeler <rwheeler@xxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Jan Kara <jack@xxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Jeff Moyer <jmoyer@xxxxxxxxxx>
[PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH] block: initialize flush request with WRITE_FLUSH instead of REQ_FLUSH
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 1/5] block: make __blk_rq_prep_clone() copy most command flags
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 5/5] block: remove the WRITE_BARRIER flag
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 3/5] dm: relax ordering of bio-based flush implementation
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCHSET 2.6.36-rc2] block, dm: finish REQ_FLUSH/FUA conversion, take#2
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH] [PATCH] option to multipath to not modify the bindinfs file
- From: Hannes Reinecke <hare@xxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: Hannes Reinecke <hare@xxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: Hannes Reinecke <hare@xxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: Christophe Varoqui <christophe.varoqui@xxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: Hannes Reinecke <hare@xxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: Hannes Reinecke <hare@xxxxxxx>
[PATCH 2/5] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Hannes Reinecke <hare@xxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Hannes Reinecke <hare@xxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: "Stamper, Brian P. (ARC-D)[Logyx LLC]" <brian.p.stamper@xxxxxxxx>
Re: [PATCH] block: QUEUE_FLAG_CLUSTER and no_cluster are NOT in sync
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [PATCH] block: Set stacked device's bounce_gfp same as that of the underlying device
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: "Stamper, Brian P. (ARC-D)[Logyx LLC]" <brian.p.stamper@xxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: Malahal Naineni <malahal@xxxxxxxxxx>
[PATCH] imported patch propagate-bounce-gfp-to-stacked-drivers.patch
- From: Malahal Naineni <malahal@xxxxxxxxxx>
[PATCH] block: blk_phys_contig_segment() doesn't account for bounce pages
- From: Malahal Naineni <malahal@xxxxxxxxxx>
[PATCH] imported patch sync-no_cluster-with-cluster-flag.patch
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: "Stamper, Brian P. (ARC-D)[Logyx LLC]" <brian.p.stamper@xxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [PATCH 2/4] dm: implement REQ_FLUSH/FUA support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 2/4] dm: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: "Stamper, Brian P. (ARC-D)[Logyx LLC]" <brian.p.stamper@xxxxxxxx>
multipath-tools/libmultipath dict.c parser.c p ...
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCH 2/4] dm: implement REQ_FLUSH/FUA support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: "Stamper, Brian P. (ARC-D)[Logyx LLC]" <brian.p.stamper@xxxxxxxx>
Re: oblem with lvm and multipath on fedora 13
- From: Malahal Naineni <malahal@xxxxxxxxxx>
oblem with lvm and multipath on fedora 13
- From: "Stamper, Brian P. (ARC-D)[Logyx LLC]" <brian.p.stamper@xxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Jan Kara <jack@xxxxxxx>
[PATCH 2/4] dm: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [PATCH] block: update documentation for REQ_FLUSH / REQ_FUA
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH] [PATCH] option to multipath to not modify the bindinfs file
- From: Christophe Varoqui <christophe.varoqui@xxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: [PATCH] [PATCH] option to multipath to not modify the bindinfs file
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH] block: update documentation for REQ_FLUSH / REQ_FUA
- From: Christoph Hellwig <hch@xxxxxx>
[PATCH UPDATED 24.5/30] jbd2: Modify ASYNC_COMMIT code to not rely on queue draining on barrier
- From: Tejun Heo <teheo@xxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 24.5/30] jbd2: Modify ASYNC_COMMIT code to not rely on queue draining on barrier
- From: Tejun Heo <teheo@xxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Jan Kara <jack@xxxxxxx>
Re: [RFC] training mpath to discern between SCSI errors
- From: Mike Christie <michaelc@xxxxxxxxxxx>
Re: DM manual failback doesn't work on RHEL5
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [PATCHSET 2.6.36-rc2] block, fs: replace HARDBARRIER with FLUSH/FUA
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Christoph Hellwig <hch@xxxxxx>
[RFC] training mpath to discern between SCSI errors (was: Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush)
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 29/30] block: remove the BLKDEV_IFL_BARRIER flag
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH 26/30] ext4: do not send discards as barriers
- From: Christoph Hellwig <hch@xxxxxx>
[PATCH 29/30] block: remove the BLKDEV_IFL_BARRIER flag
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 10/30] block: implement REQ_FLUSH/FUA based interface for FLUSH/FUA requests
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 09/30] block: rename barrier/ordered to flush
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 19/30] xfs: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 03/30] block: kill QUEUE_ORDERED_BY_TAG
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 20/30] btrfs: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 24/30] jbd: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 17/30] md: implment REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 28/30] swap: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 27/30] fat: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 16/30] lguest: replace VIRTIO_F_BARRIER support with VIRTIO_F_FLUSH support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 14/30] block/loop: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 07/30] block: drop barrier ordering by queue draining
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 26/30] ext4: do not send discards as barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 08/30] block: rename blk-barrier.c to blk-flush.c
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 18/30] block: pass gfp_mask and flags to sb_issue_discard
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 12/30] block: use REQ_FLUSH in blkdev_issue_flush()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 23/30] nilfs2: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 05/30] block: remove spurious uses of REQ_HARDBARRIER
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 30/30] block: remove the BH_Eopnotsupp flag
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 22/30] reiserfs: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCHSET 2.6.36-rc2] block, fs: replace HARDBARRIER with FLUSH/FUA
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 13/30] block: simplify queue_next_fseq
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 11/30] block: filter flush bio's in __generic_make_request()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 21/30] gfs2: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 01/30] ide: remove unnecessary blk_queue_flushing() test in do_ide_request()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 15/30] virtio_blk: drop REQ_HARDBARRIER support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 06/30] block: misc cleanups in barrier code
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 25/30] jbd2: replace barriers with explicit flush / FUA usage
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 02/30] block/loop: queue ordered mode should be DRAIN_FLUSH
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH UPDATED 4/5] md: implment REQ_FLUSH/FUA support
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
[PATCH UPDATED 4/5] md: implment REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
multipath-tools ./multipath.conf.defaults libm ...
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [PATCH 4/5] md: implment REQ_FLUSH/FUA support
- From: Neil Brown <neilb@xxxxxxx>
multipath-tools/multipath mpath_wait multipath ...
- From: bmarzins@xxxxxxxxxxxxxx
DM manual failback doesn't work on RHEL5
- From: <Yanqing_Liu@xxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Ric Wheeler <rwheeler@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Sergey Vlasov <vsu@xxxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Ric Wheeler <rwheeler@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH] block: simplify queue_next_fseq
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Ric Wheeler <rwheeler@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
[just.for.lkml@xxxxxxxxxxxxxx: 2.6.36-rc1 hangs during XFS barrier test for /]
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Chris Mason <chris.mason@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Ric Wheeler <rwheeler@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Ric Wheeler <rwheeler@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 3/5] lguest: replace VIRTIO_F_BARRIER support with VIRTIO_F_FLUSH support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 2/5 UPDATED] virtio_blk: drop REQ_HARDBARRIER support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
Re: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
Re: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs
- From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs
- From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
Performance impact of CONFIG_SCHED_MC? direct-io test case
- From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
Performance impact of CONFIG_DEBUG? direct-io test case
- From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
Re: [PATCH 03/11] block: deprecate barrier and replace blk_queue_ordered() with blk_queue_flush()
- From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
[PATCH 03/11] block: deprecate barrier and replace blk_queue_ordered() with blk_queue_flush()
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 2/5] virtio_blk: implement REQ_FLUSH/FUA support
- From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Re: [PATCH 03/11] block: deprecate barrier and replace blk_queue_ordered() with blk_queue_flush()
- From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Re: [REVISED PULL REQUEST] md updates for 2.6.36
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
Re: [PATCH REPOST RFC] relaxed barriers
- From: Tejun Heo <teheo@xxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <teheo@xxxxxxx>
Re: [PATCH REPOST RFC] relaxed barriers
- From: Tejun Heo <teheo@xxxxxxx>
Re: [PATCH 2/5] virtio_blk: implement REQ_FLUSH/FUA support
- From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Tao Ma <tao.ma@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
snapshots of mirror problems
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [PATCH v2] dm-throttle: new device mapper target to throttle reads and writes
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 08/11] block: rename barrier/ordered to flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 08/11] block: rename barrier/ordered to flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 08/11] block: rename barrier/ordered to flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 2/5] virtio_blk: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 08/11] block: rename barrier/ordered to flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH 2/5] virtio_blk: implement REQ_FLUSH/FUA support
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH v2] dm-throttle: new device mapper target to throttle reads and writes
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Christoph Hellwig <hch@xxxxxx>
[PATCH v2] dm-throttle: new device mapper target to throttle reads and writes
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 2/5] virtio_blk: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 2/5] virtio_blk: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH] [PATCH] option to multipath to not modify the bindinfs file
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [BUG] multipath-tools: uuid has become meaningless
- From: Malahal Naineni <malahal@xxxxxxxxxx>
pvmove hangs
- From: "Allen, Jack" <Jack.Allen@xxxxxxxxxxxx>
Re: [PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 2/5] virtio_blk: implement REQ_FLUSH/FUA support
- From: Christoph Hellwig <hch@xxxxxx>
[PATCH 5/5] dm: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 1/5] block/loop: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[RFC PATCHSET block#for-2.6.36-post] block: convert to REQ_FLUSH/FUA
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 2/5] virtio_blk: implement REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 4/5] md: implment REQ_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 3/5] lguest: replace VIRTIO_F_BARRIER support with VIRTIO_F_FLUSH/FUA support
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH UPDATED 10/11] fs, block: propagate REQ_FLUSH/FUA interface to upper layers
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [lvm-devel] linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Jeff Chua <jeff.chua.linux@xxxxxxxxx>
Re: [lvm-devel] linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: [lvm-devel] linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Jeff Chua <jeff.chua.linux@xxxxxxxxx>
Re: [lvm-devel] linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
Re: linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Jeff Chua <jeff.chua.linux@xxxxxxxxx>
Re: linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Jeff Chua <jeff.chua.linux@xxxxxxxxx>
Re: linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
linux-2.6.35+ causes LVM to fail with " device-mapper: version ioctl failed: Inappropriate ioctl for device"
- From: Jeff Chua <jeff.chua.linux@xxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH 03/11] block: deprecate barrier and replace blk_queue_ordered() with blk_queue_flush()
- From: "hch@xxxxxx" <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH 02/11] block: kill QUEUE_ORDERED_BY_TAG
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH 02/11] block: kill QUEUE_ORDERED_BY_TAG
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH} dm-throttle: new device mapper target to throttle reads and writes
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [PATCH 10/11] fs, block: propagate REQ_FLUSH/FUA interface to upper layers
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH 10/11] fs, block: propagate REQ_FLUSH/FUA interface to upper layers
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 10/11] fs, block: propagate REQ_FLUSH/FUA interface to upper layers
- From: Jan Kara <jack@xxxxxxx>
Re: [PATCH] dm-throttle: new device mapper target to throttle reads and writes
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [PATCH} dm-throttle: new device mapper target to throttle reads and writes
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH} dm-throttle: new device mapper target to throttle reads and writes
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH] dm-throttle: new device mapper target to throttle reads and writes
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH 05/11] block: misc cleanups in barrier code
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 01/11] block/loop: queue ordered mode should be DRAIN_FLUSH
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 04/11] block: remove spurious uses of REQ_HARDBARRIER
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 02/11] block: kill QUEUE_ORDERED_BY_TAG
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 09/11] block: implement REQ_FLUSH/FUA based interface for FLUSH/FUA requests
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 07/11] block: rename blk-barrier.c to blk-flush.c
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 11/11] block: use REQ_FLUSH in blkdev_issue_flush()
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 06/11] block: drop barrier ordering by queue draining
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 10/11] fs, block: propagate REQ_FLUSH/FUA interface to upper layers
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 08/11] block: rename barrier/ordered to flush
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH} dm-throttle: new device mapper target to throttle reads and writes
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
[git pull] device-mapper patches for 2.6.36
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
multipath-tools/multipath multipath.conf.5
- From: bmarzins@xxxxxxxxxxxxxx
multipath-tools/libmultipath discovery.c
- From: bmarzins@xxxxxxxxxxxxxx
Re: [REVISED PULL REQUEST] md updates for 2.6.36
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH] dm-throttle: new device mapper target to throttle reads and writes
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [REVISED PULL REQUEST] md updates for 2.6.36
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Re: [PATCH} dm-throttle: new device mapper target to throttle reads and writes
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH} dm-throttle: new device mapper target to throttle reads and writes
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH} dm-throttle: new device mapper target to throttle reads and writes
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [Patch] scsi_dh_rdac: retry IO for 06/3f/03 in rdac_check_sense fn
- From: Chandra Seetharaman <sekharan@xxxxxxxxxx>
[REVISED PULL REQUEST] md updates for 2.6.36
- From: Neil Brown <neilb@xxxxxxx>
multipath-tools ./multipath.conf.defaults libm ...
- From: bmarzins@xxxxxxxxxxxxxx
multipath-tools ./multipath.conf.defaults libm ...
- From: bmarzins@xxxxxxxxxxxxxx
multipath-tools/multipathd main.c
- From: bmarzins@xxxxxxxxxxxxxx
Re: [PATCH REPOST RFC] relaxed barriers
- From: Christoph Hellwig <hch@xxxxxx>
[PULL REQUEST] md updates for 2.6.36
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH, RFC] relaxed barriers
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH, RFC] relaxed barriers
- From: Tejun Heo <tj@xxxxxxxxxx>
Questions about dm-raid isw (device naming and partition table)
- From: tormen <tormen@xxxxxxx>
How does dm-raid isw compare to other linux software raid solutions (e.g. mdadm)?
- From: tormen <tormen@xxxxxxx>
Re: dm: Fixes memory leak in setup_indexes function
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH] dm: Fixes memory leak in setup_indexes function
- From: Shahzad Hussain Bangash <ext-shahzad.bangash@xxxxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Jeff Moyer <jmoyer@xxxxxxxxxx>
Re: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Chris Mason <chris.mason@xxxxxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Jeff Moyer <jmoyer@xxxxxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Jeff Moyer <jmoyer@xxxxxxxxxx>
Re: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Chris Mason <chris.mason@xxxxxxxxxx>
Re: [PATCH 2/2] dm-kcopyd: Delayed unplug of queues
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [PATCH 1/2] dm-kcopyd: Remove BIO_RW_SYNCIO flag
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Josef Bacik <josef@xxxxxxxxxx>
Re: direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs]
- From: Chris Mason <chris.mason@xxxxxxxxxx>
[PATCH] : Fix for memory leak in setup indexes
- From: Shahzad Hussain Bangash <ext-shahzad.bangash@xxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs
- From: Neil Brown <neilb@xxxxxxx>
Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs
- From: Valdis.Kletnieks@xxxxxx
Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [PATCH, RFC 2/2] dm: support REQ_FLUSH directly
- From: Christoph Hellwig <hch@xxxxxx>
[PATCH, RFC 1/2] relaxed cache flushes
- From: Christoph Hellwig <hch@xxxxxx>
Re: [PATCH] multipath: add fast_io_fail and dev_loss_tmo config parameters
- From: Benjamin Marzinski <bmarzins@xxxxxxxxxx>
Re: [PATCH] coda: rename REQ_* to CODA_REQ_*
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
[PATCH] coda: rename REQ_* to CODA_REQ_*
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 1/2 block#for-2.6.36] bio, fs: update RWA_MASK, READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 1/2 block#for-2.6.36] bio, fs: update RWA_MASK, READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
Re: [PATCH 1/2 block#for-2.6.36] bio, fs: update RWA_MASK, READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Jens Axboe <axboe@xxxxxxxxx>
[PATCH 2/2 block#for-2.6.36] bio, fs: separate out bio_types.h and define READ/WRITE constants in terms of BIO_RW_* flags
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 1/2 block#for-2.6.36] bio, fs: update RWA_MASK, READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH 3/3] dm: separate device deletion from dm_put()
- From: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx>
Re: [RFC 1/2] block: implement an unprep function corresponding directly to prep
- From: Mark Lord <kernel@xxxxxxxxxxxx>
Re: [PATCH] multipath: add fast_io_fail and dev_loss_tmo config parameters
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Jens Axboe <axboe@xxxxxxxxx>
[PATCH RESEND 2/2 block#for-linus] bio, fs: separate out bio_types.h and define READ/WRITE constants in terms of BIO_RW_* flags
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH RESEND 2/2 block#for-linus] bio, fs: separate out bio_types.h and define READ/WRITE constants in terms of BIO_RW_* flags
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH RESEND 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 2/2 block#for-linus] bio, fs: separate out bio_types.h and define READ/WRITE constants in terms of BIO_RW_* flags
- From: Tejun Heo <tj@xxxxxxxxxx>
[PATCH 1/2 block#for-linus] bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
- From: Tejun Heo <tj@xxxxxxxxxx>
[Patch] scsi_dh_rdac: retry IO for 06/3f/03 in rdac_check_sense fn
- From: "Chauhan, Vijay" <Vijay.Chauhan@xxxxxxx>
Re: RAID/block regression starting from 2.6.32, bisected
- From: Neil Brown <neilb@xxxxxxx>
Re: [PATCH] ext4: fix freeze deadlock under IO
- From: "Ted Ts'o" <tytso@xxxxxxx>
Re: [PATCH]md:dm.c Fix warning: statement with no effect
- From: "Justin P. Mattock" <justinmattock@xxxxxxxxx>
Re: [PATCH]md:dm.c Fix warning: statement with no effect
- From: "Justin P. Mattock" <justinmattock@xxxxxxxxx>
Re: [PATCH]md:dm.c Fix warning: statement with no effect
- From: "Justin P. Mattock" <justinmattock@xxxxxxxxx>
Re: [PATCH]md:dm.c Fix warning: statement with no effect
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: [PATCH 0/6] scsi_dh : Couple of fixes for scsi device handlers
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
Re: [PATCH 0/6] scsi_dh : Couple of fixes for scsi device handlers
- From: Shyam Iyer <shyam_iyer@xxxxxxxx>
Re: [PATCH 0/6] scsi_dh : Couple of fixes for scsi device handlers
- From: Chandra Seetharaman <sekharan@xxxxxxxxxx>
Re: [PATCH 2/6] scsi_dh : increment the refcounts while calling activate
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
Re: [PATCH 0/6] scsi_dh : Couple of fixes for scsi device handlers
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
Re: RAID/block regression starting from 2.6.32, bisected
- From: Tejun Heo <tj@xxxxxxxxxx>
Re: [PATCH] multipath: add fast_io_fail and dev_loss_tmo config parameters
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
Re: [PATCH 3/6] scsi_dh : release the refcounts in scsi_dh_alua handler when activate is complete
- From: James Bottomley <James.Bottomley@xxxxxxx>
Re: [PATCH 2/6] scsi_dh : increment the refcounts while calling activate
- From: James Bottomley <James.Bottomley@xxxxxxx>
Re: [PATCH 0/6] scsi_dh : Couple of fixes for scsi device handlers
- From: Chandra Seetharaman <sekharan@xxxxxxxxxx>
Re: [PATCH 0/6] scsi_dh : Couple of fixes for scsi device handlers
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
Re: [PATCH 0/6] scsi_dh : Couple of fixes for scsi device handlers
- From: Chandra Seetharaman <sekharan@xxxxxxxxxx>
[PATCH] Add support for dm-mod module autoloading
- From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
[PATCH 0/8] The DM part of dm-raid45
- From: NeilBrown <nfbrown@xxxxxxxxxx>
[PATCH 5/8] dm-raid456: add suspend/resume method
- From: NeilBrown <nfbrown@xxxxxxxxxx>
[PATCH 1/8] md/dm: create dm-raid456 module using md/raid5
- From: NeilBrown <nfbrown@xxxxxxxxxx>
[PATCH 7/8] dm-dirty-log: allow log size to be different from target size.
- From: NeilBrown <nfbrown@xxxxxxxxxx>
Re: [RFC 1/2] block: implement an unprep function corresponding directly to prep
- From: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
Re: [PATCH v2] scsi: address leak in scsi_setup_discard_cmnd error path (was: Re: scsi: unify the error handling of the prep functions)
- From: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
[PATCH 2/8] dm-raid456: add congestion checking.
- From: NeilBrown <nfbrown@xxxxxxxxxx>
[PATCH]md:dm.c Fix warning: statement with no effect
- From: "Justin P. Mattock" <justinmattock@xxxxxxxxx>
Re: [RFC 1/2] block: implement an unprep function corresponding directly to prep
- From: Mark Lord <kernel@xxxxxxxxxxxx>
Re: [RFC 1/2] block: implement an unprep function corresponding directly to prep
- From: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
Re: [RFC 1/2] block: implement an unprep function corresponding directly to prep
- From: Mark Lord <kernel@xxxxxxxxxxxx>
Re: [PATCH v2] scsi: address leak in scsi_setup_discard_cmnd error path
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
[PATCH] scsi: unify the error handling of the prep functions
- From: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
Re: disallow FS recursion from sb_issue_discard allocation
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
[PATCH 8/8] dm-raid456: switch to use dm_dirty_log for tracking dirty regions.
- From: NeilBrown <nfbrown@xxxxxxxxxx>
[PATCH 4/8] dm-raid456: add support for setting IO hints.
- From: NeilBrown <nfbrown@xxxxxxxxxx>
[PATCH 3/8] dm-raid456: support unplug
- From: NeilBrown <nfbrown@xxxxxxxxxx>
Re: [PATCH v2] scsi: address leak in scsi_setup_discard_cmnd error path
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
[PATCH 6/8] dm-raid456: add message handler.
- From: NeilBrown <nfbrown@xxxxxxxxxx>
Re: scsi: address leak in the error path of discard page allocation
- From: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
Re: [BUG] please PLEASE UnSubscribe!!!
- From: W S <whatisee1@xxxxxxxxx>
RAID/block regression starting from 2.6.32, bisected
- From: Vladislav Bolkhovitin <vst@xxxxxxxx>
Re: [PATCH 2/6] scsi_dh : increment the refcounts while calling activate
- From: Shyam Iyer <shyam_iyer@xxxxxxxx>
Re: disallow FS recursion from sb_issue_discard allocation
- From: "Ted Ts'o" <tytso@xxxxxxx>
[PATCH 1/6] scsi_dh : rename and export __detach_handler
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
[PATCH 5/6] scsi_dh : release the refcounts in scsi_dh_hp_sw handler when activate is complete
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
[PATCH 6/6] scsi_dh : release the refcounts in scsi_dh_rdac handler when activate is complete
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
[PATCH 0/6] scsi_dh : Couple of fixes for scsi device handlers
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
[PATCH 2/6] scsi_dh : increment the refcounts while calling activate
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
[PATCH] scsi_dh_rdac : Adding MODULE VERSION for rdac device handler
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
[PATCH 4/6] scsi_dh : release the refcounts in scsi_dh_emc handler when activate is complete
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
[PATCH 3/6] scsi_dh : release the refcounts in scsi_dh_alua handler when activate is complete
- From: "Moger, Babu" <Babu.Moger@xxxxxxx>
[PATCH 1/2 v2] dm stripe: move sector translation to a function
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: BIO_RW_SYNCIO
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH 1.5/2 v2] dm stripe: optimize sector division
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 1.5/2] dm-stripe: optimize sector division
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
[PATCH] dm: use dm_target_offset in targets
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 1.5/2] dm-stripe: optimize sector division
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [OT] How to associate pci id with wwpn for an hba
- From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
Re: BIO_RW_SYNCIO
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: BIO_RW_SYNCIO
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [OT] How to associate pci id with wwpn for an hba
- From: Jonathan Barber <jonathan.barber@xxxxxxxxx>
[OT] How to associate pci id with wwpn for an hba
- From: Gianluca Cecchi <gianluca.cecchi@xxxxxxxxx>
Re: BIO_RW_SYNCIO
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH] [RFC] dm-multipath: typo, strncat instead of strncpy
- From: Malahal Naineni <malahal@xxxxxxxxxx>
Re: [PATCH 2/2 v2] dm stripe: enable discard support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH 2/2 v2] dm stripe: enable discard support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 1.5/2] dm-stripe: optimize sector division
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: BIO_RW_SYNCIO
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH 2/2] dm-stripe: discard support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH 1.5/2] dm-stripe: optimize sector division
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
[PATCH 2/2] dm-stripe: discard support
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
[PATCH 1/2] dm-stripe: move sector translation to a function
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
[PATCH v3 12/12] dm stripe: enable efficient discard support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: BIO_RW_SYNCIO
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: disallow FS recursion from sb_issue_discard allocation
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH v2 10/12] block: update request stacking methods to support discards
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH] disallow FS recursion from sb_issue_discard allocation
- From: "Ted Ts'o" <tytso@xxxxxxx>
Re: BIO_RW_SYNCIO
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
BIO_RW_SYNCIO
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
[PATCH v3 06/12] dm: split discard requests on target boundaries
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 05/12] dm: factor max_io_len for code reuse
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v3 11/12] dm mpath: enable discard support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: rq-based mpath failed path on SCSI target failure (malformed discard)
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: rq-based mpath failed path on SCSI target failure (malformed discard)
- From: Mike Christie <michaelc@xxxxxxxxxxx>
Re: rq-based mpath failed path on SCSI target failure (malformed discard)
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
rq-based mpath failed path on SCSI target failure (malformed discard)
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v2 04/12] dm: use common __issue_target_request for flush and discard support
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH v2 03/12] dm: remove the DM_TARGET_SUPPORTS_DISCARDS feature flag
- From: Mike Snitzer <snitzer@xxxxxxxxxx>

[Index of Archives] [DM Crypt] [Fedora Desktop] [ATA RAID] [Fedora Marketing] [Fedora Packaging] [Fedora SELinux] [Yosemite Discussion] [KDE Users] [Fedora Docs]