From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4A004C433FE for ; Mon, 14 Feb 2022 10:02:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344357AbiBNKCP (ORCPT ); Mon, 14 Feb 2022 05:02:15 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:54748 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345614AbiBNKBq (ORCPT ); Mon, 14 Feb 2022 05:01:46 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 921551C13D for ; Mon, 14 Feb 2022 01:47:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1644832076; 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: in-reply-to:in-reply-to:references:references; bh=I2qt3+FoK96nE1glGYDfvHEmytroL36t21/ibFTNEps=; b=I3tCx2NzDNA1q6vIs7LOkp2j0mXmFAeGrU/xHQ5uRLC68yPNEZ7NsSULKabC5ywni1SsF4 dkwcLxbrSo9W43cYZUTK3hMfF86ckJRiISjxKNhkwZF71SOD5RCjNMj6upl2uc0vK0htis JR7aKpD+0U+s5lYgjWcPDT7kn63t+RQ= Received: from mail-pf1-f199.google.com (mail-pf1-f199.google.com [209.85.210.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-83-c75S6v5FMK6C5IeyQWz09w-1; Mon, 14 Feb 2022 04:47:55 -0500 X-MC-Unique: c75S6v5FMK6C5IeyQWz09w-1 Received: by mail-pf1-f199.google.com with SMTP id e18-20020aa78252000000b004df7a13daeaso11394123pfn.2 for ; Mon, 14 Feb 2022 01:47:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=I2qt3+FoK96nE1glGYDfvHEmytroL36t21/ibFTNEps=; b=eQ9zclF/BTwULF/IJ1TuhtDX+KWZNyYj2tpj5qKPr2PMrUAFwdfzkHWgM/8iP4L/pN /KAhqKjJ3863AGGWXCmooaHVS2zRtBcC3k60yqEuMaekpfrUtMfNd65kUp2Ahl0wdtXQ XDqfL6rorev0FanU0LHUS/mq1PIiGtqphZ2DBKp5pDbSuImPSaA/3aYIOjOENmBp8GiL KWc8CoAnBxRRAfaDhfFaUTtV96xXeEhFCRwPRCw//dRHjgSUKVzc193PHKoTUzow/cmM p9+tiBT/W2QrfjFb+DHDbP/Tcoj7yusHRMOGCgmXEG4LRpC47Pc27uxEjA0fSA+6Jf3V AvIQ== X-Gm-Message-State: AOAM530KwBsmIhSuLQkdV5UfrxZ2mj4haz2SGBKefyRoPjGq6EJpLhpD P5/TkpfPYIsM45xjwqZiloXgl6JECE8buJpXXjjzRwp3XkvV1bcK/FIzFxzYiYKHbVLgwJeq89V UOPpzFaBREqSJE1P5ADxuFO+YFqIyPHlq3n+2Ng== X-Received: by 2002:a17:90b:4c8e:: with SMTP id my14mr303751pjb.71.1644832073353; Mon, 14 Feb 2022 01:47:53 -0800 (PST) X-Google-Smtp-Source: ABdhPJwQupS/3/0kv1fHvOOXQWpZzGEaHDzvb3gSL3UfrXE+v/ScWqXHLMS34+5bhifcaRICK6lLTkW+L/Vg/M6cE5Q= X-Received: by 2002:a17:90b:4c8e:: with SMTP id my14mr303737pjb.71.1644832073109; Mon, 14 Feb 2022 01:47:53 -0800 (PST) MIME-Version: 1.0 References: <3c86dc88-97d9-5a71-20e1-a90279f47db5@grimberg.me> <84208be5-a7a9-5261-398c-fa9bda3efbe3@grimberg.me> <9f115198-bafc-be4e-1c90-06444b8a37f6@grimberg.me> <42ccd095-b552-32f7-96b0-d34d46f7c83e@grimberg.me> <162ec7c5-9483-3f53-bd1c-502ff5ac9f87@nvidia.com> <3292547e-2453-0320-c2e7-e17dbc20bbdd@nvidia.com> <2D31D2FB-BC4B-476A-9717-C02E84542DFA@oracle.com> <4BB6D957-6C18-4E58-A622-0880007ECD9F@oracle.com> In-Reply-To: <4BB6D957-6C18-4E58-A622-0880007ECD9F@oracle.com> From: Yi Zhang Date: Mon, 14 Feb 2022 17:47:40 +0800 Message-ID: Subject: Re: [bug report] NVMe/IB: reset_controller need more than 1min To: Max Gurtovoy , Sagi Grimberg Cc: Haakon Bugge , Max Gurtovoy , "open list:NVM EXPRESS DRIVER" , OFED mailing list Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org Hi Sagi/Max Here are more findings with the bisect: The time for reset operation changed from 3s[1] to 12s[2] after commit[3], and after commit[4], the reset operation timeout at the second reset[5], let me know if you need any testing for it, thanks. [1] # time nvme reset /dev/nvme0 real 0m3.049s user 0m0.000s sys 0m0.006s [2] # time nvme reset /dev/nvme0 real 0m12.498s user 0m0.000s sys 0m0.006s [3] commit 5ec5d3bddc6b912b7de9e3eb6c1f2397faeca2bc (HEAD) Author: Max Gurtovoy Date: Tue May 19 17:05:56 2020 +0300 nvme-rdma: add metadata/T10-PI support [4] commit a70b81bd4d9d2d6c05cfe6ef2a10bccc2e04357a (HEAD) Author: Hannes Reinecke Date: Fri Apr 16 13:46:20 2021 +0200 nvme: sanitize KATO setting- [5] # time nvme reset /dev/nvme0 real 0m12.628s user 0m0.000s sys 0m0.006s # time nvme reset /dev/nvme0 real 1m15.617s user 0m0.000s sys 0m0.006s #dmesg [ 1866.068377] nvme nvme0: creating 40 I/O queues. [ 1870.367851] nvme nvme0: mapped 40/0/0 default/read/poll queues. [ 1870.370949] nvme nvme0: new ctrl: NQN "testnqn", addr 172.31.0.202:4420 [ 1930.981494] nvme nvme0: resetting controller [ 1939.316131] nvme nvme0: creating 40 I/O queues. [ 1943.605427] nvme nvme0: mapped 40/0/0 default/read/poll queues. [ 1953.708327] nvme nvme0: resetting controller [ 2024.985591] nvme nvme0: I/O 7 QID 0 timeout [ 2024.990979] nvme nvme0: Property Set error: 881, offset 0x14 [ 2025.031069] nvme nvme0: creating 40 I/O queues. [ 2029.321798] nvme nvme0: mapped 40/0/0 default/read/poll queues.