Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp8200870rwd; Tue, 20 Jun 2023 11:33:38 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4OSTE7cGlW+l2mrSIu83xdbfyXsaD1c5BFqn587XOeRiDMxoMWLAH/nBzmCHYRBArB47FS X-Received: by 2002:a17:902:ab56:b0:1b0:5e0f:16a5 with SMTP id ij22-20020a170902ab5600b001b05e0f16a5mr9486389plb.11.1687286018144; Tue, 20 Jun 2023 11:33:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687286018; cv=none; d=google.com; s=arc-20160816; b=OwQQ0GTbFf/vHokRhQYKYNYME5pmdHErzuaiJ8uMsmy1LNPrX0yHnIzMb0jpGk2HG8 QgHCzi/Qm8OoTfFgC7gwMGEWUtcn7WGa29Yw3v66ecPk0kGPFzhbre/ONtvTaUKZ9mu0 Fld9vsgiwYc7TSDCiXuSSZHyPfyhQzox51M5xeqqEnlnDKppF4xuyR/4JlUb30ZZQ7oF GuCgxXhXwZA4YsLCqC+wleiWkcTmYcU5kB0lTebmJx5cOAwcNkhGDTUnQgaGvoTXGCjg yrQUnHyHf2onGSCwmndKv2TecdWHi8jkAsn6wFFnObxWH6gAfE6tBjvsj0qlvl8B/Y2h pTpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=gQMScDX/cvgFRjCGIqLHXDTtERLukXLjwnsLxfJ35pI=; b=zjAyTw6VglFuz2nhdKsiBR+QYSzS9ZTqyomC6UKo0ZYdCzmQoHQbuh6Gnf32vyipIi FCdEHJoGigtmAgQD441K9HDrtT/nXuK1z+KDXH4my2AKQv/RuavaknwvpMJMldiXnm+n zUES9SX8f1dDc2lCbFM02uppPxX2ODJa+6fxtEexyoEORw6g4yxHjJ0s/3WFlazkuxCU I9c4RfKBemv7IXmi3ONIMd5UlsURCGyScYCzkNZr3Ac9OlF4ZAnrkAqT0Dw62gnow9mL tkpo0pi4ysWc2afDlfh7wteeCEpyvu3G17nvqXtndzvWCOfk0/u+VN+fyuw1uQlzZevU Z4+Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=rXYzckEA; dkim=neutral (no key) header.i=@suse.de; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h20-20020a170902f2d400b001b5006b87c0si2253702plc.139.2023.06.20.11.33.25; Tue, 20 Jun 2023 11:33:38 -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; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=rXYzckEA; dkim=neutral (no key) header.i=@suse.de; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229875AbjFTRhr (ORCPT + 99 others); Tue, 20 Jun 2023 13:37:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37284 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229585AbjFTRhq (ORCPT ); Tue, 20 Jun 2023 13:37:46 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7AC8F4; Tue, 20 Jun 2023 10:37:45 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 8D9611F390; Tue, 20 Jun 2023 17:37:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1687282664; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gQMScDX/cvgFRjCGIqLHXDTtERLukXLjwnsLxfJ35pI=; b=rXYzckEAd/l0kJ6YfTeJZg+wCkmRdBLJw+hsF38Y+EoKp8QkwqmTXIGeD2ViXZfzTOTdEq 8hTq2EbCpTiZB/mzgnd6hDcKITLPZ5Kifz6/BaILvMXYTFa+bIEBIw2Bb3e7fMXYWm7Cg7 OvNH7suvloGx3Cywr5diI5eRlzlwlJY= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1687282664; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gQMScDX/cvgFRjCGIqLHXDTtERLukXLjwnsLxfJ35pI=; b=ns9MlZGHKJUhM/aNne/k5Ws/X7/tyzNRTdXuOac/x2eUDnoTTbJ0BAEtPmUfqYluuO+4dx 8imqchkZwihWjsAw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 6C5E21346D; Tue, 20 Jun 2023 17:37:44 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id TYX+GejjkWSAMAAAMHmgww (envelope-from ); Tue, 20 Jun 2023 17:37:44 +0000 Date: Tue, 20 Jun 2023 19:37:43 +0200 From: Daniel Wagner To: Sagi Grimberg Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Chaitanya Kulkarni , Shin'ichiro Kawasaki , Hannes Reinecke , James Smart , Martin Belanger Subject: Re: [PATCH blktests v1 1/3] nvme/048: Check for queue count check directly Message-ID: References: <20230620132703.20648-1-dwagner@suse.de> <20230620132703.20648-2-dwagner@suse.de> <380cde65-8794-cfbc-237f-30a8d7e9330c@grimberg.me> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <380cde65-8794-cfbc-237f-30a8d7e9330c@grimberg.me> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 Tue, Jun 20, 2023 at 04:49:45PM +0300, Sagi Grimberg wrote: > > +nvmf_wait_for_queue_count() { > > + local subsys_name="$1" > > + local queue_count="$2" > > + local nvmedev > > + > > + nvmedev=$(_find_nvme_dev "${subsys_name}") > > + > > + queue_count_file="/sys/class/nvme-fabrics/ctl/${nvmedev}/queue_count" > > + > > + nvmf_wait_for_state "${subsys_name}" "live" || return 1 > > + > > + queue_count=$((queue_count + 1)) > > + if grep -q "${queue_count}" "${queue_count_file}"; then > > + return 0 > > + fi > > + > > + echo "expected queue count ${queue_count} not set" > > + return 1 > > +} > > + > > set_nvmet_attr_qid_max() { > > local nvmet_subsystem="$1" > > local qid_max="$2" > > @@ -56,10 +76,7 @@ set_qid_max() { > > local qid_max="$3" > > set_nvmet_attr_qid_max "${subsys_name}" "${qid_max}" > > - > > - # Setting qid_max forces a disconnect and the reconntect attempt starts > > - nvmf_wait_for_state "${subsys_name}" "connecting" || return 1 > > - nvmf_wait_for_state "${subsys_name}" "live" || return 1 > > + nvmf_wait_for_queue_count "${subsys_name}" "${qid_max}" || return 1 > > Why not simply wait for live? The connecting is obviously racy... That is what the new version is doing. It's waiting for the live state and then checks the queue count.