Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp2592694iog; Sun, 19 Jun 2022 23:41:55 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vH9AqY0d2nnusK2959eGIXYbN4PmrxZy6GQcCnM4wmRqRFXa4AynjpVYBmWjhJuJzvrY3C X-Received: by 2002:a17:906:c797:b0:711:8c01:32d4 with SMTP id cw23-20020a170906c79700b007118c0132d4mr19533553ejb.205.1655707315211; Sun, 19 Jun 2022 23:41:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655707315; cv=none; d=google.com; s=arc-20160816; b=Fm9/GPic66UNJk87d61DsyYK6N+5TFJ+0QR0BjRThlCzknx86vlqetJs8AYponIxkL D/dt8o57hZsHQd8LpNMQqVLvl3DoieRXm9dlG6QjQrNPdahd5LdDRh4HWEAPVbDllrFL nkMgJSq5BDpFrh0uLyKL5gPPlvrXkRNVWIF/8gjHrnKqbghyTPq5RBbwKqKo+hblu0SD r2728DzWf8q+irgZOtvjudj+GNadYHFLDj+L6zK1pG9wUTS9iWKX3Nix+FnzhXyI2gd9 1Ddq6QcUGYdrSuu4q1OfEFqxQt15G7kyB5nvj4eL8dvaDVdR0eP+ZDhxOt+YnmfHoIsW 2ImA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=Ot/7qHAxNArg0WwUyr4ngGXd8cwSiu8CSyM6SKe/Q6w=; b=JLfE0F3grIWK5oJX8yYV1LiiYCtAZbhbsZf0qKgNLWfYZVfi6pxKqnQZVDZOIK8EwA 2/B3BmJpncoLDrrjPgN7AqfhjB7byEZInK10XE03ILkVhMRl9HHTnRuc0/m2xJS8gpfe PXG55eNizXZ3+GsgpyArjDKejneZ8jNEnNOFVFe3Vsrgqmjg6N3O5LOnxe2unoxXB7RR nKBgNBBaL42d3LEBls8zEA13as7HjqDAtWhaWhlboaGoBxPN1Rlthdhywwhm8hwjSlZ4 nJJ8Bqg6DbK8ULqNHyg+wP7RBjQ6zDVZHYa44pWNpwfdoL9d6/sYrAvXshnGcGqW8ai5 6M7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k20-20020aa7d8d4000000b004356b3746d1si6392140eds.71.2022.06.19.23.41.29; Sun, 19 Jun 2022 23:41:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238377AbiFTG3K (ORCPT + 99 others); Mon, 20 Jun 2022 02:29:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53220 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238464AbiFTG2g (ORCPT ); Mon, 20 Jun 2022 02:28:36 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 96DC363FE; Sun, 19 Jun 2022 23:28:32 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 9D91C6732D; Mon, 20 Jun 2022 08:28:28 +0200 (CEST) Date: Mon, 20 Jun 2022 08:28:28 +0200 From: Christoph Hellwig To: Hannes Reinecke Cc: Damien Le Moal , John Garry , axboe@kernel.dk, jejb@linux.ibm.com, martin.petersen@oracle.com, brking@us.ibm.com, hch@lst.de, linux-block@vger.kernel.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, chenxiang66@hisilicon.com Subject: Re: [PATCH RFC v2 03/18] scsi: core: Implement reserved command handling Message-ID: <20220620062828.GA10753@lst.de> References: <1654770559-101375-1-git-send-email-john.garry@huawei.com> <1654770559-101375-4-git-send-email-john.garry@huawei.com> <88d192b5-741b-7104-7f72-0178aa18bafb@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <88d192b5-741b-7104-7f72-0178aa18bafb@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 20, 2022 at 08:24:24AM +0200, Hannes Reinecke wrote: > So my idea for SATA is simply _not_ to use reserved tags. > Any TMF functions (or the equivalent thereof) should always be sent as > non-NCQ commands. And when doing so we're back to QD=1 on SATA anyway, so > there _must_ be tags available. Consequently the main reason for having > reserved tags (namely to guarantee that tags are available for TMF) doesn't > apply here. At least in the non-elevator case (which includes all passthrough I/O) request have tags assigned as soon as they are allocated. So, we absolutely can have all tags allocated and then need to do a TMF.