Re: [dm-devel] [PATCH 00/33] multipath-tools fixes from SUSE

2017-03-22 Thread Christophe Varoqui
Pending. I plan to merge the rest tomorrow. Le 22 mars 2017 8:02 PM, "Xose Vazquez Perez" a écrit : > On 02/28/2017 05:22 PM, Martin Wilck wrote: > > > As announced previously, here comes a collection of multipath-tools > patches > > that SUSE is using for SLES12 SP2. >

Re: [dm-devel] [PATCH 00/33] multipath-tools fixes from SUSE

2017-03-22 Thread Xose Vazquez Perez
On 02/28/2017 05:22 PM, Martin Wilck wrote: > As announced previously, here comes a collection of multipath-tools patches > that SUSE is using for SLES12 SP2. >From this bundle, only 19 of them were merged. 14 are missing, or ...pending? -- dm-devel mailing list dm-devel@redhat.com

[dm-devel] [PATCH 1/2] md: add raid4/5/6 journal mode API (for dm-raid use)

2017-03-22 Thread heinzm
From: Heinz Mauelshagen Upstream commit 2ded370373a400c20cf0c6e941e724e61582a867 started the addition of "write-back" mode to MD (raid5-cache), i.e. support write-back caching on the raid journal device. In order to allow the dm-raid target to switch between the available

[dm-devel] [PATCH 2/2] dm raid: add raid4/5/6 journal mode support

2017-03-22 Thread heinzm
From: Heinz Mauelshagen Upstream commit 7a771ceac771d009f7203c40b256b0608d7ea2f8 added journal support to close the raid4/5/6 "write hole". Uitilizing prerequisite "md: add raid4/5/6 journal mode API (for dm-raid use)", add support to switch the journal device cache mode

[dm-devel] [PATCH 0/2] md/dm-raid: add/use API to switch raid4/5/6 journal cache modes

2017-03-22 Thread heinzm
From: Heinz Mauelshagen Upstream commit 7a771ceac771d009f7203c40b256b0608d7ea2f8 added journal support to dm-raid to close the raid4/5/6 "write hole" but doesn't provide an API to switch modes from device-mapper. Add missing API to MD and use it from device-mapper dm-raid

Re: [dm-devel] [PATCH] block: trace completion of all bios.

2017-03-22 Thread Christoph Hellwig
On Wed, Mar 22, 2017 at 01:38:09PM +1100, NeilBrown wrote: > > Currently only dm and md/raid5 bios trigger trace_block_bio_complete(). > Now that we have bio_chain(), it is not possible, in general, for a > driver to know when the bio is really complete. Only bio_endio() > knows that. > > So