From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "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>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [virtio-dev] Re: RE: [PATCH v13] virtio-net: support device stats
Date: Mon, 31 Jul 2023 13:50:10 +0800 [thread overview]
Message-ID: <1690782610.3048255-3-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <PH0PR12MB548149ED4C687913EDA3EED9DC05A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Mon, 31 Jul 2023 04:32:22 +0000, Parav Pandit <parav@nvidia.com> wrote:
>
> > From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > Sent: Thursday, July 27, 2023 7:18 AM
>
> > > why don't we have a config space field for supported types?
> > > more straight forward than complex rules...
> >
> > I am ok for adding a config space field.
>
> During 1.3 we completed the discussion that any new config field addition must adhere to DMA interface and not a register.
> Multiple capabilities need this.
> So lets please work on that.
OK.
>
> Counters needs to use the dma interface and it can wait one time to utilize the modern interface.
>
> 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.
I will keep pushing this, if your proposals affect this, I will fix it in
a furture version.
Thanks.
>
>
---------------------------------------------------------------------
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-31 5:52 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 ` Xuan Zhuo [this message]
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
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=1690782610.3048255-3-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
/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