Re: [dm-devel] [PATCH 2/2] dm-writecache

On Mon, 27 Nov 2017, Dan Williams wrote: > On Mon, Nov 27, 2017 at 8:01 PM, Mikulas Patocka wrote: > > > > > > > > On Fri, 24 Nov 2017, Dan Williams wrote: > > > > > On Wed, Nov 22, 2017 at 6:36 PM, Mikulas Patocka > > > wrote: > > > > Hi > > > > > >

Re: [dm-devel] [PATCH 0/4] path latency prio fixes

On 2017/12/4 23:11, Martin Wilck wrote: > On Mon, 2017-12-04 at 22:23 +0800, Guan Junxiong wrote: >>> An open question is what multipathd should do wrt path grouping if >>> it >>> only has preliminary prio values, in particular with group_by_prio. >> For the open question, in this situation, IMO

[dm-devel] [PATCH v2] multipath-tools: output more topology info for NVMe discovery

From: Jie Yang Assign sg_id.channel to controller id of the NVMe/NVMf target and assign sg_id.lun to namespace ID of the target. Signed-off-by: Jie Yang Reviewed-by: Guan Junxiong --- change since V1: patch 2/2 --> path

Re: [dm-devel] [PATCH 0/4] path latency prio fixes

Hi Martin, Sorry for the late reply. I have recovered from a busy week. Please find my comments below. On 2017/11/23 10:10, Martin wrote: > Hi Guan, > > while staring at this code the other day, I realized another possible > issue with your latency prioritizer. > > It will cause significant

[dm-devel] [PATCH] multipath-tools: check null path before handle path-failed event

In the hot-plug storage OS, if we tear down the target storage, there is a race between the path removing from the path list and handling the path-failed udev event. Therefore, we need to check null path before handle path-failed event. Signed-off-by: Guan Junxiong ---