From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 29 Aug 2017 16:51:08 +0200 From: Christoph Hellwig To: Guan Junxiong Cc: Christoph Hellwig , Jens Axboe , Keith Busch , linux-block@vger.kernel.org, Sagi Grimberg , linux-nvme@lists.infradead.org, niuhaoxin , "Shenhong (C)" Subject: Re: [PATCH 10/10] nvme: implement multipath access to nvme subsystems Message-ID: <20170829145108.GB32673@lst.de> References: <20170823175815.3646-1-hch@lst.de> <20170823175815.3646-11-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: List-ID: On Tue, Aug 29, 2017 at 06:22:50PM +0800, Guan Junxiong wrote: > Does this introduce conflicts with current DM-Multipath used for NVMe/NVMeF > when path IO error occurs? Such IO will be retried not only on the nvme-mpath > internal path, but also on the dm-mpath path. It will not reach back to dm-multipath if we fail over here. From mboxrd@z Thu Jan 1 00:00:00 1970 From: hch@lst.de (Christoph Hellwig) Date: Tue, 29 Aug 2017 16:51:08 +0200 Subject: [PATCH 10/10] nvme: implement multipath access to nvme subsystems In-Reply-To: References: <20170823175815.3646-1-hch@lst.de> <20170823175815.3646-11-hch@lst.de> Message-ID: <20170829145108.GB32673@lst.de> On Tue, Aug 29, 2017@06:22:50PM +0800, Guan Junxiong wrote: > Does this introduce conflicts with current DM-Multipath used for NVMe/NVMeF > when path IO error occurs? Such IO will be retried not only on the nvme-mpath > internal path, but also on the dm-mpath path. It will not reach back to dm-multipath if we fail over here.