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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3ADB2C3A59E for ; Wed, 4 Sep 2019 22:00:10 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0CB0B20870 for ; Wed, 4 Sep 2019 22:00:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="GDecksIU" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0CB0B20870 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=grimberg.me Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:List-Subscribe: List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id:Message-Id:Date: Subject:To:From:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Owner; bh=PGrVGAt9f1iauxyKrlH+MJb5eApTmbLRwqBtMPA7vnY=; b=GDe cksIU/9DULcmwXZshzwYqPJeuP9oMO7QNDiuGFngMcLZLWtxixXwsyVQUx41XEXLZEETymXpuponR xxjNH4QiZA5fcyyLY/MU0XxK0Bph6L4Bp8hgH1dIZbQEjs8Na6/81bHBGkOBnfSaXm70InRSQ0l/o UimBex5kXYpD1pJHsJQ7wQmqfdDdGeRK+ELejQdy5dSkuSD293l0KDQtGWpBnd+QxFjB8FErPiY3h q1/VVU0Hj8QQnjg8kyFFA7Nmd/nMZVvsgx6YKAUDerKIYxryMiSiyyKgE6kzYzWHMHfPurjntYoyu M7JOopgmtCtvcKDfQ7U3E95OVYA5A6g==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1i5dJv-0006Pm-2u; Wed, 04 Sep 2019 22:00:07 +0000 Received: from [2600:1700:65a0:78e0:514:7862:1503:8e4d] (helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.92 #3 (Red Hat Linux)) id 1i5dJl-0005pf-Ga; Wed, 04 Sep 2019 21:59:58 +0000 From: Sagi Grimberg To: linux-nvme@lists.infradead.org Subject: [PATCH v4 0/4] Support discovery log change events Date: Wed, 4 Sep 2019 14:59:49 -0700 Message-Id: <20190904215954.15423-1-sagi@grimberg.me> X-Mailer: git-send-email 2.17.1 X-BeenThere: linux-nvme@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Keith Busch , Hannes Reinecke , Christoph Hellwig , James Smart MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org We want to be able to support discovery log change events automatically without user intervention. The definition of discovery log change events applies on "persistent" long lived controllers, so first we need to have discovery controllers to stay for a long time and accept kato value. Then when we do happen to get a discovery log change event on the persistent discovery controller, we simply fire a udev event to user-space to re-query the discovery log page and connect to new subsystems in the fabric. This works with latest nvme-cli master with the nvme-cli patch added to this series. Changes from v3: - Add nvme_class uevent callout for controller specific environment variables - send discovery just like any AEN that we send to userspace - merged discovery aen enable + send uevents to userspace into a single patch as they are now trivially adding support for the feature - Added nvme-cli modifications to handle the new information from the event Changes from v2: - added patch to always enable aen, regardless of the number of I/O queues - fixes line over 80 characters Changes from v1: - rebase to nvme-5.3 - pass none if trsvcid is uninitialized - pass NVME_CTRL_NAME instead of NVME_CTRL_INSTANCE Sagi Grimberg (4): nvme-fabrics: allow discovery subsystems accept a kato nvme: enable aen regardless of the presence of I/O queues nvme: add uevent variables for controller devices nvme: send discovery log page change events to userspace drivers/nvme/host/core.c | 40 ++++++++++++++++++++++++++++++++++--- drivers/nvme/host/fabrics.c | 12 ++--------- 2 files changed, 39 insertions(+), 13 deletions(-) -- 2.17.1 _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme