From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0B03D1DF967 for ; Fri, 22 Nov 2024 18:16:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1732299395; cv=none; b=g1KIYaubcKC0Ryqbr+mce/TtSI7q1OomQfV/ErjLY+NZ3qlR+dmRrz8j/HvaB/HZbKBrcCkafbOxfQgeTlXVTg94nDH6a0Z9l+oV244vDR+MxauCw/I0+QYAdm/UqqGnWRKKOExirGZDos3SINq9IHsDDo1azysAVWbDSOibSPo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1732299395; c=relaxed/simple; bh=J6AjMBq4stUpxA1GLehzZ6jucYdaDMN+nmMzN/kGObE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=RhWG7hhnYi0SsxMVtNYR+KcsGxMjLlOCrGu3syBgoiRgJKIyYdIxvBmV63qepHOySlqUqvsrRaliqdE8gETrtBNnCoxMwlpIyB4WcwTQM0/yyZLu7lpzwOifDK37U/Vbbx4/5ZbUodQ68sPlqVS1wRKJXLeSTw39bolUMc4xW9U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ABQM0Zy+; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ABQM0Zy+" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B125AC4CECE; Fri, 22 Nov 2024 18:16:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1732299394; bh=J6AjMBq4stUpxA1GLehzZ6jucYdaDMN+nmMzN/kGObE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ABQM0Zy+hC+CzT2lz+t5Ov19yrZrilxlU+5hGcXh146NneOi2dORZxBpWZGgFK/9o +f3I8XPFY/zKO5oTVo2scs/ywAX3p/hzaPN9MSiZAD72PWi+QKzV+w8pS3lx4pyaC9 9zfnV7RkcSytOuZ87K7gqoaGmkSto3cRgJGiTFiCjy0SuKDz5mZ/mauUPEytlyn/ww qy2Jb57iaHgPMAYvq5QVMiAiO9dDren8Aeuz628ckSyWb7MRghiRz1h8fN/35er5AW 2eraQz2eQBJxiBXZVUjpSDTtt1mvjcXams244vhX8bhDfe4QK5K93kQ9QXgFKEtrnc Cyl+ls1Kku5lA== Date: Fri, 22 Nov 2024 11:16:31 -0700 From: Keith Busch To: John Meneghini Cc: Christoph Hellwig , Bryan Gurney , linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, sagi@grimberg.me, axboe@kernel.dk, mpe@ellerman.id.au, naveen@kernel.org, maddy@linux.ibm.com, kernel@xen0n.name, bmarzins@redhat.com Subject: Re: [PATCH 1/1] nvme: always enable multipath Message-ID: References: <20241121220321.40616-1-bgurney@redhat.com> <20241122120925.GA25817@lst.de> <4bd8f843-6dfa-4c66-9e42-cf4245166844@redhat.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4bd8f843-6dfa-4c66-9e42-cf4245166844@redhat.com> On Fri, Nov 22, 2024 at 12:52:51PM -0500, John Meneghini wrote: > On 11/22/24 10:39, Keith Busch wrote: > > Anyway, we only use the one physical function, so they're certainly not > > multipath devices here. We disable the CONFIG option because while the > > nvme multipath IO overhead is low, it's not zero. > > Do we know what the performance impact is? Has anybody measured the difference? It doesn't benefit single path devices, so any cost for it is too high. It's clearly not free.