[dm-devel] [PATCH 3/6] multipath: there is no "none" path state

There is a "none" path checker, but not a "none" path state. Signed-off-by: Benjamin Marzinski --- libmultipath/checkers.c | 1 - 1 file changed, 1 deletion(-) diff --git a/libmultipath/checkers.c b/libmultipath/checkers.c index cd6d6a3..94d8486 100644 ---

[dm-devel] [PATCH 5/6] multipath: fix doc typo

The dev_loss_tmo cap if fast_io_fail_tmo isn't set is 600 seconds, not 300 seconds. Signed-off-by: Benjamin Marzinski --- multipath/multipath.conf.5 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5

[dm-devel] [PATCH 4/6] mutipath: updated Huawei storage config

I was given this updated built-in config by Zhou Weigang from Huawei. Signed-off-by: Benjamin Marzinski --- libmultipath/hwtable.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c index b018ddf..78de1fa

[dm-devel] [PATCH 0/6] Misc patches

The first two patches are simply reposts. Patch 3 and 5 are simple typo fixes. Patch 4 is an updated built-in config I recieved from Hauwei storage. The only large patch is 6. It adds a new paramter, "ghost_delay" that users can set if their active/passive arrays keep getting discovered in the

[dm-devel] [PATCH 6/6] multipath: add "ghost_delay" parameter

If the lower-priority passive paths for a multipath device appear first, IO can go to them and cause the hardware handler to activate them, before the higher priority paths appear, causing the devices to failback. Setting the "ghost_delay" parameter to a value greater than 0 can avoid this

[dm-devel] [PATCH 1/6] mpathpersist: Fix invalid condition check

In commit 1990257c (mpathpersist: add support for prkeys file), the check to see if mpathpersist needed to tell multipathd to update a device's prkey was wrong. It had a typo that made it evaluate to true for any service action, instead of just for registrations. This is the correct check.

[dm-devel] [PATCH 2/6] multipath: add man page info for my prkey changes

Update the man pages to list the new configuration options and multipathd commands. Signed-off-by: Benjamin Marzinski --- multipath/multipath.conf.5 | 17 + multipathd/multipathd.8| 16 2 files changed, 33 insertions(+) diff --git

[dm-devel] [PATCH] vmalloc: introduce vmap_pfn for persistent memory

Hi I am developing a driver that uses persistent memory for caching. A persistent memory device can be mapped in several discontiguous ranges. The kernel has a function vmap that takes an array of pointers to pages and maps these pages to contiguous linear address space. However, it can't be

[dm-devel] [PATCH] bio: have bio_kmap_irq return the size of mapped data (fwd)

Hi I need the function bio_kmap_irq in the driver that I am developing, but it doesn't return the size of the mapped data. I've made this patch to fix it. Mikulas From: Mikulas Patocka The function bio_kmap_irq is not usable because it does not return the size of the

Re: [dm-devel] [PATCH 0/4] dm-writecache

On Tue, Nov 07 2017 at 3:59pm -0500, Mikulas Patocka wrote: > Hi > > Here I'm sending patches for the dm-writecache target. It is for kernel > 4.14-rc8. Hi, Patches 1 - 3 look pretty straight-forward, shouldn't be hard to get them in sooner rather than later. So in

[dm-devel] [PATCH 2/4] vmalloc: introduce vmap_pfn

There's a function vmap that can take discontiguous pages and map them linearly to the vmalloc space. However, persistent memory may not be backed by pages, so we can't use vmap on it. This patch introduces a function vmap_pfn that works like vmap, but it takes an array of page frame numbers

[dm-devel] [PATCH 4/4] dm-writecache

The dm-writecache target. Signed-off-by: Mikulas Patocka --- drivers/md/Kconfig | 11 drivers/md/Makefile|1 drivers/md/dm-writecache.c | 2356 + 3 files changed, 2368 insertions(+) Index:

[dm-devel] [PATCH 3/4] swait: export the symbols __prepare_to_swait and __finish_swait

In order to reduce locking overhead, I use the spinlock in swait_queue_head to protect not only the wait queue, but also the list of events. Consequently, I need to use unlocked functions __prepare_to_swait and __finish_swait. These functions are declared in the file include/linux/swait.h, but

[dm-devel] [PATCH 1/4] bio: have bio_kmap_irq return the size of mapped data

The function bio_kmap_irq is not usable because it does not return the size of the mapped data. Fix bio_kmap_irq and __bio_kmap_irq so that they return the size of mapped data. Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer ---

[dm-devel] [PATCH 0/4] dm-writecache

Hi Here I'm sending patches for the dm-writecache target. It is for kernel 4.14-rc8. Mikulas -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel

Re: [dm-devel] Significantly dropped dm-cache performance in 4.13 compared to 4.11

On Fri, Nov 03, 2017 at 07:50:23PM +0100, Stefan Ring wrote: > It strikes me as odd that the amount read from the spinning disk is > actually more than what comes out of the combined device in the end. This suggests dm-cache is trying to promote too way too much. I'll try and reproduce the issue,

Re: [dm-devel] [PATCH] dm-crypt, dm-integrity: allow unaligned bv_offset (was: [Regression, Bisected] dm-crypt IO failures with active slub_debug in 4.12 and later)

On Mon, 6 Nov 2017 18:57:15 -0500 (EST) Mikulas Patocka wrote: > On Mon, 6 Nov 2017, Bruno Prémont wrote: > > On Mon, 6 Nov 2017 11:18:09 Mike Snitzer wrote: > > > On Thu, Nov 02 2017 at 4:39pm -0400, Bruno Prémont wrote: > > > > Hi, > > > > > > > > Between 4.11 and 4.12 I stopped being able

Re: [dm-devel] [Regression, Bisected] dm-crypt IO failures with active slub_debug in 4.12 and later

On Mon, 6 Nov 2017 11:18:09 Mike Snitzer wrote: > On Thu, Nov 02 2017 at 4:39pm -0400, Bruno Prémont wrote: > > Hi, > > > > Between 4.11 and 4.12 I stopped being able to boot my system with root > > partition encrypted with dm-crypt (issue still present in 4.14-rc7). > > The system was able to

Re: [dm-devel] [PATCH] dm-crypt, dm-integrity: allow unaligned bv_offset

On 11/07/2017 09:13 AM, Bruno Prémont wrote: >> Signed-off-by: Mikulas Patocka >> Cc: sta...@vger.kernel.org # v4.12+ >> Fixes: 8f0009a22517 ("dm crypt: optionally support larger encryption sector >> size") >> Fixes: 7eada909bfd7 ("dm: add integrity target") > >