Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp201664imm; Wed, 3 Oct 2018 14:31:38 -0700 (PDT) X-Google-Smtp-Source: ACcGV608+LIRYWVjSGkOn0hZqckq38Rymodu2DTy2M/wBZXOgF2psu0a9EvuoDGjh+KiZSvzhJsS X-Received: by 2002:a63:7419:: with SMTP id p25-v6mr2983652pgc.395.1538602298704; Wed, 03 Oct 2018 14:31:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538602298; cv=none; d=google.com; s=arc-20160816; b=pde/gXrj8AflL5wh9vvpiSXM7X+0FkgHgc9O7DzYpyg0RbsiGtDuQDXtw0/N9Ouvbs X1rz17Z17e1vCeACvGkdYxoWkTi4q0g3dy1vbg353CKOdXKrkwc3DF+wwRmgGh0UJx/n +MLuj2rfjnuodu+DBnBfGUGC9xHYREoTeLy6mV2TLJY/p3rMvzeoC/WsVWRxeasmuEKy 18Jf4PMUqSOqMPKRed7tqv8EwxG2XDo0Fsu1HDv8nAuP/t0wa8MdZ3FU8NZLjqd6ADVb PctazJ24uhRkpkMDkTDrgrN9FONGc/K35PTldGyDQ7TL3+Beh0jZKEUwIFfIg4BDKOLj RKdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=wfqomajgh6RPjLS9yhzKHrCyN9+MSmi1zi3r6dWhehM=; b=aW0s9+ypoyV6q3ES5Ju8k6ctSnl/+MQq2naaJPQEqfKHdafa1KE3gCtEHYZRqq3zyq +IK0d+u9rwrKI+EU3dhYbOa0hR87ZsgjUAfuvAsaHKvWJTHsqR8pw35/jcHHfu8Jtumc x1bP8lP2N9oePZHcemsXhGakBKk2qqdaavDagoNHWlq2d5+PsqOaICrazJuuCiyXlAMw h9Vwxf/wxw6q8FGmOdm8CrQxyHTR9bp9KMAXHnRJcfD3exXyGWe5SLjG9C+8cQdK5o+j 1H7lYZ2c3++eszERcdSkfZzzjMjpNWVtsCTnQ6PFxI33hUSuPFe20qqfyf4WZ5aGVySm ZYdg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="yEhrCgo/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id y4-v6si2744880pgo.390.2018.10.03.14.31.23; Wed, 03 Oct 2018 14:31:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="yEhrCgo/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1727115AbeJDEVE (ORCPT + 99 others); Thu, 4 Oct 2018 00:21:04 -0400 Received: from mail.kernel.org ([198.145.29.99]:50184 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725747AbeJDEVE (ORCPT ); Thu, 4 Oct 2018 00:21:04 -0400 Received: from localhost (unknown [69.71.4.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 86203213A2; Wed, 3 Oct 2018 21:30:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1538602255; bh=6HpzLxzbkVtKkb9brhi7cmOCRuIPCL1eMHcPK0rKmq4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=yEhrCgo/2uTmq7TMESGa7DtjW2Zr/kM+SVn08seG0RReNQcYFUctRVlsj9xrbQjAQ 4NLSdjkaIauCkI9MAimZSOQeX/fPoKlEr10aI4CRjBJrrHfrPg2E+13UgdUxcQ32rQ e/5LCUvAiGJyPO609l8wtPz1vONsomqk+pKopH10= Date: Wed, 3 Oct 2018 16:30:54 -0500 From: Bjorn Helgaas To: Alexandru Gagniuc Cc: linux-pci@vger.kernel.org, bhelgaas@google.com, keith.busch@intel.com, alex_gagniuc@dellteam.com, austin_bolen@dell.com, shyam_iyer@dell.com, Ariel Elior , everest-linux-l2@cavium.com, "David S. Miller" , Michael Chan , Ganesh Goudar , Jeff Kirsher , Tariq Toukan , Saeed Mahameed , Leon Romanovsky , Jakub Kicinski , Dirk van der Merwe , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org, oss-drivers@netronome.com, Stephen Hemminger , Martin Mares Subject: Re: [PATCH 1/9] PCI: sysfs: Export available PCIe bandwidth Message-ID: <20181003213054.GH120535@bhelgaas-glaptop.roam.corp.google.com> References: <20180903180242.14504-1-mr.nuke.me@gmail.com> <20180903180242.14504-2-mr.nuke.me@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180903180242.14504-2-mr.nuke.me@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [+cc Stephen, Martin (for possible lspci changes)] Hi Alexandru, On Mon, Sep 03, 2018 at 01:02:28PM -0500, Alexandru Gagniuc wrote: > For certain bandwidth-critical devices (e.g. multi-port network cards) > it is useful to know the available bandwidth to the root complex. This > information is only available via the system log, which doesn't > account for link degradation after probing. > > With a sysfs attribute, we can computes the bandwidth on-demand, and > will detect degraded links. > > Signed-off-by: Alexandru Gagniuc > --- > drivers/pci/pci-sysfs.c | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c > index 9ecfe13157c0..6658e927b1f5 100644 > --- a/drivers/pci/pci-sysfs.c > +++ b/drivers/pci/pci-sysfs.c > @@ -218,6 +218,18 @@ static ssize_t current_link_width_show(struct device *dev, > } > static DEVICE_ATTR_RO(current_link_width); > > +static ssize_t available_bandwidth_show(struct device *dev, > + struct device_attribute *attr, char *buf) > +{ > + struct pci_dev *pci_dev = to_pci_dev(dev); > + u32 bw_avail; > + > + bw_avail = pcie_bandwidth_available(pci_dev, NULL, NULL, NULL); > + > + return sprintf(buf, "%u.%03u Gb/s\n", bw_avail / 1000, bw_avail % 1000); > +} > +static DEVICE_ATTR_RO(available_bandwidth); Help me understand this. We already have these sysfs attributes: max_link_speed # eg, 16 GT/s max_link_width # eg, 8 current_link_speed # eg, 16 GT/s current_link_width # eg, 8 so I think the raw materials are already exposed. The benefits I see for this new file are that - pcie_bandwidth_available() does the work of traversing up the tree, doing the computations (link width * speed, reduced by encoding overhead), and finding the minimum, and - it re-traverses the path every time we look at it, while the boot-time check is a one-time event. In principle this could all be done in user space with the attributes that are already exported. There's some precedent for things like this in lspci, e.g., "NUMA node" [1], and lspci might even be a more user-friendly place for users to look for this, as opposed to searching through sysfs. [1] https://git.kernel.org/pub/scm/utils/pciutils/pciutils.git/commit/?id=90ec4a6d0ae8 > static ssize_t secondary_bus_number_show(struct device *dev, > struct device_attribute *attr, > char *buf) > @@ -786,6 +798,7 @@ static struct attribute *pcie_dev_attrs[] = { > &dev_attr_current_link_width.attr, > &dev_attr_max_link_width.attr, > &dev_attr_max_link_speed.attr, > + &dev_attr_available_bandwidth.attr, > NULL, > }; > > -- > 2.17.1 >