Received: by 2002:a05:6a10:c7d3:0:0:0:0 with SMTP id h19csp142046pxy; Sat, 14 Aug 2021 02:59:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwGRaqE8O2HZbMVA0SUwnyemXOtNQ7f0IJh6FucgSeg+JtVk5pqz7jFYUrySjB9ZQRgmgSi X-Received: by 2002:a17:906:5a98:: with SMTP id l24mr6548899ejq.540.1628935160494; Sat, 14 Aug 2021 02:59:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628935160; cv=none; d=google.com; s=arc-20160816; b=YNqjg1h7qM4HCmvzsje4DhicysWfBxJycbG7rqHiVbvm6j7X+p+tb8TYVkUePOE/CF f/oYcO4ox7dkiI+ah9xeXvk/BbSJ+1wmOfz9mKTBsT/XaOb5b9BX0iTjwSGxxCjP/eYT Pl/h71kZsINdl0kS3DhWWR9qBoNtFufvTog5MMfJWFiU0kUxaW2rEmxcHbeN037cXlf0 Tr2vWbGoaDXESjss1y1WsyyHY9SepUzl+DvA0IBBgXUasLu1CA6xAzT1XUbBAZi1hawe WeD/k/1evRYJyR/RcOYGO/uzqNACrQiayFIkABEHpV9U8RUu/rdTPgbnCFMS8wtgMGui EgXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=p5SnuM8qhWAUOlUCTJqfTr0kwDVsui51/u1+Yq8ky4k=; b=oZvjxOBw81rCIGnd87J1TYETnqh7GEBDCQFWwHl8+/ue+4VX9qF3msOVDWWvrCQ0+T bejMrFT6iDYZYLUvD/U12clfugvQzDlz88L+BzNaggm78WwXYSSOq9zuk4YY2+fSJh87 Yh5qpYFZl/2ZNVJgFaJH72LfSGoCs5UPoBDmVD3fUw4dB8KrXW8AfH6SIJKyHUfCI+ie 5oPxf4/uNoXySu6daP0sPcUtPbsTi5jxqK68guKFaalf5TFp9qHejY/LrNrmFa7lk1+J WfGYwnazmfow+LbzoedMr/65pYHfLFvQ3jLOyA8J7bJ5+hDySKkp/IM/IcjJwvGEUVTn xtgQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=exciBrD6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v10si4424469ejy.710.2021.08.14.02.58.57; Sat, 14 Aug 2021 02:59:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=exciBrD6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237661AbhHNJ6G (ORCPT + 99 others); Sat, 14 Aug 2021 05:58:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:37352 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229894AbhHNJ6F (ORCPT ); Sat, 14 Aug 2021 05:58:05 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0CEC260F00; Sat, 14 Aug 2021 09:57:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1628935057; bh=xWmu3S7OhqJfrbNVVEnLPn9gGWPZvZk00Od0nr+U3mE=; h=From:To:Cc:Subject:Date:From; b=exciBrD6mgJ6qsPR3T1C0+14IVEMccWVq5qMCQp1yqJq4gjOtfbEtK+eXQ9uRRhIY xa1fI7ITnMVcqK4CYQvf/S5sG6X8pBlcrfvIyvbqt4jIXJXsCWwUnY4z6NDIF44K2Z xDABUwOEWSQwEVezCoEpwANqDZHY/QrP/5Ig867OKxGhOqJxU7e9TenuCUpyVu/5cl h5ard2w5kzFFB/nr1fvpZdhV5nFJyHrLhCvha36h9njjAVimmnrCU1Ba49pK5GDF81 evZG7N9v41jA4yiW+YMfTTq4Rh1KJ9bav4nsIR6vTF5QdZDLxJogQPwuWlfg/oMQtU IOtOEzBN+6nBA== From: Leon Romanovsky To: "David S . Miller" , Jakub Kicinski Cc: Leon Romanovsky , Guangbin Huang , Jacob Keller , Jiri Pirko , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, Salil Mehta , Shannon Nelson , Yisen Zhuang , Yufeng Mo Subject: [PATCH net-next 0/6] Devlink cleanup for delay event series Date: Sat, 14 Aug 2021 12:57:25 +0300 Message-Id: X-Mailer: git-send-email 2.31.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Leon Romanovsky Hi, Jakub's request to make sure that devlink events are delayed and not printed till they fully accessible [1] requires us to implement delayed event notification system in the devlink. In order to do it, I moved some of my patches (xarray e.t.c) from the future series to be before "Move devlink_register to be near devlink_reload_enable" [2]. That allows us to rely on DEVLINK_REGISTERED xarray mark to decide if to print event or not. Other patches are simple cleanup which is needed anyway. [1] https://lore.kernel.org/lkml/20210811071817.4af5ab34@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com [2] https://lore.kernel.org/lkml/cover.1628599239.git.leonro@nvidia.com Next in the queue: * Delay event series * Move devlink_register to be near devlink_reload_enable" * Extension of devlink_ops to be set dynamically * devlink_reload_* delete * Devlink locks rework to user xarray and reference counting * ???? Thanks Leon Romanovsky (6): devlink: Simplify devlink_pernet_pre_exit call devlink: Remove check of always valid devlink pointer devlink: Count struct devlink consumers devlink: Use xarray to store devlink instances devlink: Clear whole devlink_flash_notify struct net: hns3: remove always exist devlink pointer check .../hisilicon/hns3/hns3pf/hclge_devlink.c | 8 +- .../hisilicon/hns3/hns3vf/hclgevf_devlink.c | 8 +- include/net/devlink.h | 4 +- net/core/devlink.c | 391 ++++++++++++------ 4 files changed, 273 insertions(+), 138 deletions(-) -- 2.31.1