From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
Parav Pandit <parav@nvidia.com>
Subject: Re: [virtio-dev] Re: [PATCH v12] virtio-net: support device stats
Date: Wed, 12 Jul 2023 08:33:47 -0400 [thread overview]
Message-ID: <20230712082616-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87mt01jp1b.fsf@redhat.com>
On Wed, Jul 12, 2023 at 02:24:32PM +0200, Cornelia Huck wrote:
> On Wed, Jul 12 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Wed, Jul 12, 2023 at 07:44:01PM +0800, Xuan Zhuo wrote:
> >> On Wed, 12 Jul 2023 07:34:38 -0400, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >> > On Tue, Mar 15, 2022 at 11:24:02AM +0800, Xuan Zhuo wrote:
> >> > > This patch allows the driver to obtain some statistics from the device.
> >> > >
> >> > > In the back-end implementation, we can count a lot of such information,
> >> > > which can be used for debugging and judging the running status of the
> >> > > back-end. We hope to directly display it to the user through ethtool.
> >> > >
> >> > > To get stats atomically, try to get stats for all queue pairs in one
> >> > > command.
> >> > >
> >> > > Signed-off-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> >> > > Suggested-by: Michael S. Tsirkin <mst@redhat.com>
> >> >
> >> > Functionally, I think this is close to ok now. But the text needs
> >> > of work. Are you trying to target 1.3 with this?
> >>
> >> I personally worry about that 1.3 may be too late, if possible, I would like to
> >> respond as soon as possible.
> >>
> >> I really don't really care if it can get into 1.3 or not but I do hope that this
> >> can be done as soon as possible.
> >>
> >> Thanks.
> >
> > Yes we were supposed to freeze for 1.3. This change can be merged on a
> > main branch after 1.3 forks and is under review.
>
> Nod, that's what I would prefer to do. Being merged on virtio-next
> should be enough for including device/driver implementations.
Except I'd prefer a v1.3 branch instead of a next branch - adding things
on the branch should be harder, not easier.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-07-12 12:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 3:24 [virtio-dev] [PATCH v12] virtio-net: support device stats Xuan Zhuo
2022-03-22 7:57 ` [virtio-dev] " Jason Wang
2023-07-10 7:28 ` [virtio-dev] " Xuan Zhuo
2023-07-12 8:08 ` Jason Wang
2023-07-12 9:11 ` Xuan Zhuo
2023-07-13 2:21 ` Jason Wang
2023-07-13 2:27 ` [virtio-dev] Re: [virtio-comment] " Xuan Zhuo
2023-07-12 11:34 ` [virtio-dev] " Michael S. Tsirkin
2023-07-12 11:44 ` Xuan Zhuo
2023-07-12 11:54 ` Michael S. Tsirkin
2023-07-12 12:24 ` Cornelia Huck
2023-07-12 12:33 ` Michael S. Tsirkin [this message]
2023-07-21 12:24 ` [virtio-dev] 1.3 and branching (was: [virtio-dev] Re: [PATCH v12] virtio-net: support device stats) Cornelia Huck
2023-07-21 12:41 ` [virtio-dev] " Michael S. Tsirkin
2023-07-21 13:05 ` [virtio-dev] Re: 1.3 and branching Cornelia Huck
2023-07-21 14:13 ` [virtio-dev] RE: 1.3 and branching (was: [virtio-dev] Re: [PATCH v12] virtio-net: support device stats) Parav Pandit
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=20230712082616-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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