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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 126D7C432C0 for ; Wed, 20 Nov 2019 08:52:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D708B2231D for ; Wed, 20 Nov 2019 08:52:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="EPkkd3Go" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728042AbfKTIwg (ORCPT ); Wed, 20 Nov 2019 03:52:36 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:56059 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727909AbfKTIwf (ORCPT ); Wed, 20 Nov 2019 03:52:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574239955; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=J62qG/l4OLNLTAXRiIot0/oxRSgkxGYPpqtpwxT76WA=; b=EPkkd3Gor5c1ztdylSv6lVFL3NcgTEJFR35idrTIZ4AAbvwxryeHuMSI58nPTnCh9fQ5mU RRbB0qyQ5DCqZCCjz2HvWclbk1Wm3kagNTUDMy0V7fV1vVDZ4XA+xs7/Y8BbOdIoLmTKto +5IZ1ATGAPpKf5ftmCk0Xt8nnRME5NU= Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-163-XULD-aHSMHCehqe9Bk4aGQ-1; Wed, 20 Nov 2019 03:52:32 -0500 Received: by mail-qt1-f198.google.com with SMTP id f31so16639954qta.0 for ; Wed, 20 Nov 2019 00:52:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=2B/lNGhsR+kI+KNj1BmROSKU5fUdHyUukwLs+JxNkWA=; b=S+6fsj07rYI8HvvhWCEMX0JnR0ZepvvQP9Alc7xM7CDTp9xLNfZEhRwembuJNVToRu IJYoVPx7Fq3YUhoWriV9zl55649YdQtQ3YTLuPfbTMxNrcFZ7CubJE/vCnr9AG/KWDHf LAoRZ1vjTvyHb+9A/xQgO7rgVvCvhUFYww95dlhP/lR/K3gMTjuFo4VXA7Fspuk7PSNt 3EOHJkmaQDM7wF/l64FEIPb25xbW1JGVFK9LZga4YyN/P+29IdbNmMvUSRMzSICcZIpe 5BOHp8AkvURZiVrAhn0pXMzkA0m1aqd/SrA3FmAYoBunggWfOSlz1OiUIIUH65OSnOMh /v9A== X-Gm-Message-State: APjAAAXILW4sBoRFG0hsuf8EW9fYHmcAtdlM1UVtxSM1FE23YlhOEoIM /0BSJP7VhbVV8UDdhElRg/KsavCDrNiggOO96WpXepvRS1dcU8+FB8SYbjV9c21+ESJEhhcocQm AYRB7OfPz4Xo1Eu/x X-Received: by 2002:a05:620a:536:: with SMTP id h22mr1355406qkh.480.1574239951668; Wed, 20 Nov 2019 00:52:31 -0800 (PST) X-Google-Smtp-Source: APXvYqzCWyR6HUb5BbPq5DUZXyuyXDuw6pH0/t6iz3hUQgrSdlnaDkRyBd3Abw0ar+8jKbMeqfRFaw== X-Received: by 2002:a05:620a:536:: with SMTP id h22mr1355383qkh.480.1574239951357; Wed, 20 Nov 2019 00:52:31 -0800 (PST) Received: from redhat.com (bzq-79-176-6-42.red.bezeqint.net. [79.176.6.42]) by smtp.gmail.com with ESMTPSA id m186sm574902qkc.39.2019.11.20.00.52.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Nov 2019 00:52:30 -0800 (PST) Date: Wed, 20 Nov 2019 03:52:23 -0500 From: "Michael S. Tsirkin" To: Parav Pandit Cc: Jason Wang , Jeff Kirsher , "davem@davemloft.net" , "gregkh@linuxfoundation.org" , Dave Ertman , "netdev@vger.kernel.org" , "linux-rdma@vger.kernel.org" , "nhorman@redhat.com" , "sassmann@redhat.com" , "jgg@ziepe.ca" , Kiran Patil , Alex Williamson , Tiwei Bie Subject: Re: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus Message-ID: <20191120034839-mutt-send-email-mst@kernel.org> References: <20191115223355.1277139-1-jeffrey.t.kirsher@intel.com> <13946106-dab2-6bbe-df79-ca6dfdeb4c51@redhat.com> <743601510.35622214.1574219728585.JavaMail.zimbra@redhat.com> MIME-Version: 1.0 In-Reply-To: X-MC-Unique: XULD-aHSMHCehqe9Bk4aGQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, Nov 20, 2019 at 03:38:18AM +0000, Parav Pandit wrote: >=20 >=20 > > From: Jason Wang > > Sent: Tuesday, November 19, 2019 9:15 PM > >=20 > > ----- Original Message ----- > > > > > > > > > > From: Jason Wang > > > > Sent: Tuesday, November 19, 2019 1:37 AM > > > > > > > > > > Nop. Devlink is NOT net specific. It works at the bus/device level. > > > Any block/scsi/crypto can register devlink instance and implement the > > > necessary ops as long as device has bus. > > > > >=20 > > Well, uapi/linux/devlink.h told me: > >=20 > > " > > * include/uapi/linux/devlink.h - Network physical device Netlink inter= face " > >=20 > > And the userspace tool was packaged into iproute2, the command was name= d > > as "TC", "PORT", "ESWITCH". All of those were strong hints that it was = network > > specific. Even for networking, only few vendors choose to implement thi= s. > >=20 > It is under iproute2 tool but it is not limited to networking. Want to fix the documentation then? That's sure to confuse people ... --=20 MST