Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp112156pxa; Tue, 11 Aug 2020 19:10:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz8i67u95QQ5nFvzQM3xSFVNfjPHXQPP/aMSDGisR2GBaG9HdW/brxZiqYY+wTtEH4M3/zj X-Received: by 2002:a50:d80b:: with SMTP id o11mr7308927edj.148.1597198254239; Tue, 11 Aug 2020 19:10:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597198254; cv=none; d=google.com; s=arc-20160816; b=0HpZfdInWIETO0WmQc4IEEVQIKQDq/nHnzJ5pqRZufsXnuhRYAN8gxRo/a30fT+3Ul OkttpdNp8qASg2QZw3X31EkrzmUKwzRRG1QpyyH4QXPf6V2wzVH4TBDluLP57i+GZo6f KH9UWCZ3/GyWvLMeiMg5MnfKCdZYhZEDof6ZDB1Ov9sta4NKvi4oP3HIx3iDchh56Jxw PGIJCNiPCkD9VcdFsJj8NMNg+KuLeajUJ8zMpoBTYv5G0e+5C8Z2zoXFuD2OJHlnvu6Q A/CrysibF1qFBnxbE7zQ5yqnSIoYIHyhms+70LLAe5Hiz/cuuYm1t60/q9fDyGise+FL U6lA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=CjBAia3ospUg/zmTq94JkNk1GKssjuXqjxy8UFfaMgA=; b=HdeuqDbG6qUF8LgHhjfWlLxjEmjenZ8kFi9BzL9XvZuoMyo3nBOp70WDg2j6mYlKTt aQ+y1BKYIlJO/IQMkJR8Ev6s/WjRnrms/yu28JCTHYfaepNe2cTrgOMYKSSTk+WnrLOg RDrfeVKBkZL7R2KuoSNumUZH8qPTtnMaI2SNDCMMd2EzEFWWHFxi8FvBadZ8Jlr7wgcu MfqqEVCa9poyNLGzJI6G1KeQzjECx7ebeNRvW2GqrqwN1fP4x6CxgPccAT6N84ZEkVst KnamqfcyOnstaWbJ5ixS1xgd+267pkMMXTvwORa4+ME1IYBRFctYt6idCZ1muFk/2GEw hhnA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JbNAZH2D; 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id rl7si221837ejb.264.2020.08.11.19.10.30; Tue, 11 Aug 2020 19:10:54 -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=@redhat.com header.s=mimecast20190719 header.b=JbNAZH2D; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726489AbgHLCJf (ORCPT + 99 others); Tue, 11 Aug 2020 22:09:35 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:21475 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726255AbgHLCJf (ORCPT ); Tue, 11 Aug 2020 22:09:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1597198173; 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=CjBAia3ospUg/zmTq94JkNk1GKssjuXqjxy8UFfaMgA=; b=JbNAZH2De6VMBHVnkpb4TqPjkY0I9NjgAf/cjaS5U/J6qCdfrZpVFrp9Bp3qCuI2ajh+Ro ZATBBZ1NfCcZfqw7ZPsPf8xrWvMF+FDwYBkmn3zK4QjyjMPQkaXxU7ctkPqiT9k1B3kBDb H6VeiT7tlJUxsvTbyye/8QZPbR2ubFM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-350-hLK4A1mUMWylNewyGM9dsg-1; Tue, 11 Aug 2020 22:09:32 -0400 X-MC-Unique: hLK4A1mUMWylNewyGM9dsg-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9E88A102C7F5; Wed, 12 Aug 2020 02:09:30 +0000 (UTC) Received: from [10.72.12.118] (ovpn-12-118.pek2.redhat.com [10.72.12.118]) by smtp.corp.redhat.com (Postfix) with ESMTP id EACC087D62; Wed, 12 Aug 2020 02:09:23 +0000 (UTC) Subject: Re: VDPA Debug/Statistics To: Eli Cohen , "Michael S. Tsirkin" Cc: "kvm@vger.kernel.org" , "virtualization@lists.linux-foundation.org" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "eli@mellanox.com" , "lulu@redhat.com" , Majd Dibbiny , Maor Dickman , Shahaf Shuler , Parav Pandit References: <20200811073144-mutt-send-email-mst@kernel.org> From: Jason Wang Message-ID: <02c1cf02-40c7-80d7-60b5-19b691993018@redhat.com> Date: Wed, 12 Aug 2020 10:09:22 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/8/11 下午7:58, Eli Cohen wrote: > On Tue, Aug 11, 2020 at 11:26:20AM +0000, Eli Cohen wrote: >> Hi All >> >> Currently, the only statistics we get for a VDPA instance comes from the virtio_net device instance. Since VDPA involves hardware acceleration, there can be quite a lot of information that can be fetched from the underlying device. Currently there is no generic method to fetch this information. >> >> One way of doing this can be to create a the host, a net device for >> each VDPA instance, and use it to get this information or do some >> configuration. Ethtool can be used in such a case The problems are: - vDPA is not net specific - vDPA should be transparent to host networking stack >> >> I would like to hear what you think about this or maybe you have some other ideas to address this topic. >> >> Thanks, >> Eli > Something I'm not sure I understand is how are vdpa instances created on mellanox cards? There's a devlink command for that, is that right? > Can that be extended for stats? > > Currently any VF will be probed as VDPA device. We're adding devlink support but I am not sure if devlink is suitable for displaying statistics. We will discuss internally but I wanted to know why you guys think. I agree with Michael, if it's possible, integrating stats with devlink should be the best. Having another interface with is just for stats looks not good. Thanks > > -- > MST >