From: Greg KH <gregkh@linuxfoundation.org>
To: kys@microsoft.com
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
jasowang@redhat.com, leann.ogasawara@canonical.com,
marcelo.cerri@canonical.com, sthemmin@microsoft.com
Subject: Re: [PATCH V2 3/4] vmbus: add per-channel sysfs info
Date: Mon, 18 Sep 2017 15:59:55 +0200 [thread overview]
Message-ID: <20170918135955.GD21077@kroah.com> (raw)
In-Reply-To: <20170918035419.11062-3-kys@exchange.microsoft.com>
On Sun, Sep 17, 2017 at 08:54:18PM -0700, kys@exchange.microsoft.com wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
>
> This extends existing vmbus related sysfs structure to provide per-channel
> state information. This is useful when diagnosing issues with multiple
> queues in networking and storage.
>
> The existing sysfs only displayed information about the primary
> channel. The one place it reported multiple channels was the
> channel_vp_mapping file which violated the sysfs convention
> of one value per file.
>
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> Documentation/ABI/stable/sysfs-bus-vmbus | 56 ++++++++++
> drivers/hv/channel_mgmt.c | 10 +-
> drivers/hv/hyperv_vmbus.h | 2 +
> drivers/hv/vmbus_drv.c | 185 +++++++++++++++++++++++++++++--
> include/linux/hyperv.h | 6 +
> 5 files changed, 246 insertions(+), 13 deletions(-)
Feels like a new feature to me, and not needed in 4.14-final.
thanks,
greg k-h
next prev parent reply other threads:[~2017-09-18 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 3:49 [PATCH V2 0/4] Drivers: hv: Miscellaneous fixes kys
2017-09-18 3:54 ` [PATCH V2 1/4] vmbus: don't acquire the mutex in vmbus_hvsock_device_unregister() kys
2017-09-18 3:54 ` [PATCH V2 2/4] Drivers: hv: fcopy: restore correct transfer length kys
2017-09-18 13:59 ` Greg KH
2017-09-18 3:54 ` [PATCH V2 3/4] vmbus: add per-channel sysfs info kys
2017-09-18 13:59 ` Greg KH [this message]
2018-10-18 15:19 ` Olaf Hering
2018-10-18 15:32 ` Michael Kelley
2018-10-18 16:41 ` Stephen Hemminger
2018-10-18 16:39 ` Stephen Hemminger
2017-09-18 3:54 ` [PATCH V2 4/4] Drivers: hv: vmbus: Expose per-channel event counters events counters kys
2017-09-18 13:59 ` Greg KH
2017-09-18 13:57 ` [PATCH V2 1/4] vmbus: don't acquire the mutex in vmbus_hvsock_device_unregister() Greg KH
2017-09-18 14:00 ` Greg KH
2017-09-18 14:43 ` KY Srinivasan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170918135955.GD21077@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox