Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2515703imu; Mon, 19 Nov 2018 01:40:36 -0800 (PST) X-Google-Smtp-Source: AJdET5fnBGS7ZcqwDvA+lqsZAFG+viJfOCsvSIctw0muJqex3Uu4wxMwCe5JHPWMECp0EEpSyB5v X-Received: by 2002:a62:25c2:: with SMTP id l185-v6mr22899673pfl.64.1542620436684; Mon, 19 Nov 2018 01:40:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542620436; cv=none; d=google.com; s=arc-20160816; b=SLtY3CjmJmQqqcmVuw5xHHCGhmUHjIJgnf01NTrdJWIbj+A8LymXZdQcpYjpUPE75f Ozw2vrHAYHedV3csC4tSNTXovJI6E4S6fO34Dz1Upw+gLqi/N3+EqrN+xxUjJ5f04irI geAKtEOxKDXvY8zlsXXSFeuGg88yOuGZHSdf5zWBpybR9z7lclD44RSt+lJOBnWG+FGv LGy1Swm30l+CaaJMcgkm5h+b97g98mvd7lv7e2szOO20yxI2Mu1mAX+fvPGt0L0MRMSQ c0M1tCNwBKWUok5H3L2RVKjZhjAqja7mySXAPBD0FA9QTN4FfnNWUCwKSZjUs+sVjhuc PXvw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=b3HESKyOOaQ/Av/g/yQKR21J5kv2y5vGhkXHzFc311I=; b=SGDuZv3X/VtGOC/Keipp0gctwFh/UHYDNozgTmdXXa+fGfpRp9MGTukGTiSM10iHuV ohE8dGDpCCR0M+NUCJN701clITnO4QK3jzYCL5jJrYZ+8iDJXNSjyGJgcsQ/wb5+6IMx hugZRf4CwF6Upi3PLhQ3QPjs19gczv+tQeO5tG3DojxO5KPXYcXtO8BTr9ki8ru2Y8qg Hpm+bTFZvJ6ceu5LBKn40l/rO8CpfjnsnEkl52UZBAbFafa4fVr/6QYrsm6kYtraB6WC a6O9nEbUWTKsIALdkw2mGQDIjeQyLUF2/qjp4H3X69jbpae2QLuBlInGQ96GQFO72VD/ /pMQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c76si26769670pga.70.2018.11.19.01.40.19; Mon, 19 Nov 2018 01:40:36 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727547AbeKSUCp (ORCPT + 99 others); Mon, 19 Nov 2018 15:02:45 -0500 Received: from verein.lst.de ([213.95.11.211]:36995 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727450AbeKSUCo (ORCPT ); Mon, 19 Nov 2018 15:02:44 -0500 Received: by newverein.lst.de (Postfix, from userid 2407) id 9480268AFE; Mon, 19 Nov 2018 10:39:38 +0100 (CET) Date: Mon, 19 Nov 2018 10:39:38 +0100 From: Christoph Hellwig To: Mike Snitzer Cc: Christoph Hellwig , Hannes Reinecke , linux-nvme@lists.infradead.org, Keith Busch , Sagi Grimberg , axboe@kernel.dk, Martin Wilck , lijie , xose.vazquez@gmail.com, chengjike.cheng@huawei.com, shenhong09@huawei.com, dm-devel@redhat.com, wangzhoumengjian@huawei.com, christophe.varoqui@opensvc.com, bmarzins@redhat.com, sschremm@netapp.com, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: nvme: allow ANA support to be independent of native multipathing Message-ID: <20181119093938.GA11757@lst.de> References: <30cf7af7-8826-55bd-e39a-4f81ed032f6d@suse.de> <20181114174746.GA18526@redhat.com> <87c931e5-4ac9-1795-8d40-cc5541d3ebcf@suse.de> <20181115174605.GA19782@redhat.com> <20181116091458.GA17267@lst.de> <37098edd-4dea-b58f-bca6-3be9af8ec4ee@suse.de> <20181116094947.GA19296@lst.de> <20181116101752.GA21531@lst.de> <20181116192802.GA30057@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181116192802.GA30057@redhat.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 16, 2018 at 02:28:02PM -0500, Mike Snitzer wrote: > You rejected the idea of allowing fine-grained control over whether > native NVMe multipathing is enabled or not on a per-namespace basis. > All we have is the coarse-grained nvme_core.multipath=N knob. Now > you're forecasting removing even that. Please don't do that. The whole point is that this hook was intended as a band aid for the hypothetical pre-existing setups. Not ever for new development. > Please, PLEASE take v2 of this patch.. please? ;) See the previous mail for the plan ahead. I'm sick and tired of you trying to sneak your new developemts back in.