From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 50AF73DEAD7 for ; Tue, 3 Mar 2026 14:20:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772547659; cv=none; b=dFJ0Qa/xm+zf2SxCLLtH3sZNwu9oqJHTr0v7IlNiE8QqnnnpoayNf8ePhj8zEPC6jUsJG9EsuSLF8sSJc4AMJkmqVNu0dlfo11inh4VIOjS3l02gsriyN27ZCIHXQwE73OxWbu5kpJQ6k3B5foB7LHqZivHR9OWKD5nxgxDDvdg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772547659; c=relaxed/simple; bh=IkQ7/gyK0kZ4FalknuXom3D+eyJvw5c+6TIGp5/qhI8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=cg+FX4tj++r9fAv5RkqnduVLHJag5NJgxGvmgfrMgD9+vxmQXmS+CGTGbnXyxdg7lDrO802KMgXD5ftiF+QgCKdzz3T7kqEcmGgjzJYGIf9HGLOsOQ6W5tZfmJUDAVozuQW54nKyPoSMqKG8LAIWUdWIZWSrTZa6uR1FuFlFTcE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=AbSFPFgb; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="AbSFPFgb" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1772547657; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hpscGlqtT0S5hsz/lvyVjD4lT80PmJ0j11LCHkWNSX8=; b=AbSFPFgbi32e2Q39mdcQVI2XMQgjt6p0Qr8T71aLPtsAUP9gCgAR/fJ2JxCKVIr/O9lFWu paz81aZGm2BI5NIBBv9pu9LiGW5Kt+FtPL0tUapdAdPISovzyclEMgTdse5L9vkQbXAgav vsZDWUjVgilBcPuVB/ygRf9cHfbKDpM= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-127-3ehT5qksMqaYvuvFq6SAhg-1; Tue, 03 Mar 2026 09:20:52 -0500 X-MC-Unique: 3ehT5qksMqaYvuvFq6SAhg-1 X-Mimecast-MFC-AGG-ID: 3ehT5qksMqaYvuvFq6SAhg_1772547649 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id B940B1956095; Tue, 3 Mar 2026 14:20:48 +0000 (UTC) Received: from bmarzins-01.fast.eng.rdu2.dc.redhat.com (unknown [10.6.23.247]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 632EE1800590; Tue, 3 Mar 2026 14:20:47 +0000 (UTC) Received: from bmarzins-01.fast.eng.rdu2.dc.redhat.com (localhost [127.0.0.1]) by bmarzins-01.fast.eng.rdu2.dc.redhat.com (8.18.1/8.17.1) with ESMTPS id 623EKkZo1889507 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 3 Mar 2026 09:20:46 -0500 Received: (from bmarzins@localhost) by bmarzins-01.fast.eng.rdu2.dc.redhat.com (8.18.1/8.18.1/Submit) id 623EKibS1889506; Tue, 3 Mar 2026 09:20:44 -0500 Date: Tue, 3 Mar 2026 09:20:44 -0500 From: Benjamin Marzinski To: Hannes Reinecke Cc: John Garry , hch@lst.de, kbusch@kernel.org, sagi@grimberg.me, axboe@fb.com, martin.petersen@oracle.com, james.bottomley@hansenpartnership.com, hare@suse.com, jmeneghi@redhat.com, linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org, michael.christie@oracle.com, snitzer@kernel.org, dm-devel@lists.linux.dev, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 02/24] scsi-multipath: introduce basic SCSI device support Message-ID: References: <20260225153627.1032500-1-john.g.garry@oracle.com> <20260225153627.1032500-3-john.g.garry@oracle.com> <784abca8-9dc1-4fca-b72f-62d55b4cc3f1@oracle.com> <003612c1-ff07-466c-93e8-d7766a9ec2db@suse.de> 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=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <003612c1-ff07-466c-93e8-d7766a9ec2db@suse.de> X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 On Tue, Mar 03, 2026 at 09:01:04AM +0100, Hannes Reinecke wrote: > On 3/3/26 06:39, Benjamin Marzinski wrote: > > On Mon, Mar 02, 2026 at 11:39:28AM +0000, John Garry wrote: > > > On 02/03/2026 02:22, Benjamin Marzinski wrote: > > > > > diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig > > > > > index 19d0884479a24..cfab7ad1e3c2c 100644 > > > > > --- a/drivers/scsi/Kconfig > > > > > +++ b/drivers/scsi/Kconfig > > > > > @@ -76,6 +76,16 @@ config SCSI_LIB_KUNIT_TEST > > > > > If unsure say N. > > > > > +config SCSI_MULTIPATH > > > > > + bool "SCSI multipath support" > > > > At least until this supports ALUA, it should probably be marked > > > > EXPERIMENTAL, just so people trying it out aren't surprised if it > > > > doesn't multipath their device in the way they expect. > > > > > > I think that ALUA support will be mainline acceptance criteria, and I am > > > looking to add it now. > > > > > > BTW, Hannes suggested to not use the DH ALUA support, so that means to > > > separate out the core ALUA support from the DH stuff. So you have any > > > opinion on that approach? > > > > I would (perhaps naively) have thought that the device handlers would be > > a useful abstraction for dealing with ALUA devices. But, Hannes knows > > this code much better than me. like I said before, I'm no scsi expert. > > > The main point of the device handlers was to inject a 'start' command > whenever paths needed to be switched (Like you need to do for some > active/passive arrays). > But that really caused quite some issues with complexity, as you easily > can get into array path ping-pong on path failure with no I/O being > transmitted. > > So for this implementation I would stick with implicit ALUA > (most modern implementations have done so already anyway), and > then there's no need using the device handlers. That makes sense. Limiting support to implicit ALUA significantly lowers the bar for getting ALUA working. AFAICS, It should just require getting the path selecting code right. -Ben > > Cheers, > > Hannes > -- > Dr. Hannes Reinecke Kernel Storage Architect > hare@suse.de +49 911 74053 688 > SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg > HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich