From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>
Subject: [virtio-dev] Re: [PATCH v13] virtio-net: support device stats
Date: Mon, 31 Jul 2023 05:12:00 -0400 [thread overview]
Message-ID: <20230731050908-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB548149ED4C687913EDA3EED9DC05A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Mon, Jul 31, 2023 at 04:32:22AM +0000, Parav Pandit wrote:
> I have two proposals to for the dma interface and we should discuss that in separate thread to not mix the cvq parts of the stats.
> I will start the thread shortly and put pointer to this requirement of counters + many others that we are discussing including ntuple.
Great! I agree it is best to discuss infrastructure work like this
now while we are in freeze. Merge this early on 1.4 branch so
everything else can depend on it.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2023-07-31 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 8:12 [virtio-dev] [PATCH v13] virtio-net: support device stats Xuan Zhuo
2023-07-26 11:17 ` [virtio-dev] " Michael S. Tsirkin
2023-07-27 1:48 ` Xuan Zhuo
2023-07-31 4:32 ` [virtio-dev] " Parav Pandit
2023-07-31 5:50 ` [virtio-dev] " Xuan Zhuo
2023-07-31 6:19 ` [virtio-dev] " Parav Pandit
2023-07-31 9:13 ` [virtio-dev] " Michael S. Tsirkin
2023-07-31 7:01 ` [virtio-dev] " Jason Wang
2023-07-31 9:12 ` Michael S. Tsirkin [this message]
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=20230731050908-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--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