Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Jason Wang <jasowang@redhat.com>,
	"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	Shahaf Shuler <shahafs@nvidia.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	"hengqi@linux.alibaba.com" <hengqi@linux.alibaba.com>
Subject: Re: [virtio-comment] Re: [virtio] RE: [virtio-comment] proposal: use admin command (and aq) of the device to query config space
Date: Wed, 2 Aug 2023 08:09:42 -0400	[thread overview]
Message-ID: <20230802075851-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DM8PR12MB5480CBCB70621CD6BEF5222FDC0BA@DM8PR12MB5480.namprd12.prod.outlook.com>

On Wed, Aug 02, 2023 at 11:56:11AM +0000, Parav Pandit wrote:
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Wednesday, August 2, 2023 5:21 PM
> 
> > 
> > There's one thing to say about putting everything in one place, and that is that
> > one can then find everything in one place.
> 
> When a device grows incrementally and each functionality also, 
> grouping it per functionality gives better pace to keep things self-contained.
> 
> Think how messy a set command would be if all 3 functionality in one set command.
> 
> > For example, at the moment we actually do have a problem with cvq, and the
> > problem is that it sets internal device state that is not observable (unlike original
> > pre-1.0 config space which was writeable).
> > 
> Which part is not observable?

e.g. rss config.

> > 
> > By the way there's a pci express ECN for relaxed ordering or something like this.
> > I am yet to look at it, I wonder whether it can be used to avoid the issues we
> > have with MMIO in a way that is easier to use than DMA.
> 
> Waiting to deliver new features on new PCI standard will drastically slow down virtio.

features? surely not. but when we are building a new transport then
we are building for the future, it takes years for a new
transport to be deployed.

> I don't think its good idea, but I would like to know about such ECN, if there is one.

I am talking about unordered IO (UIO) ECN.


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  reply	other threads:[~2023-08-02 12:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  7:09 [virtio-comment] proposal: use admin command (and aq) of the device to query config space Parav Pandit
2023-08-02  4:20 ` [virtio-comment] " Michael S. Tsirkin
2023-08-02  4:33   ` [virtio-comment] " Parav Pandit
2023-08-02  8:45   ` [virtio-comment] " Zhu, Lingshan
2023-08-02  8:59     ` [virtio-comment] " Parav Pandit
2023-08-02  9:40       ` [virtio-comment] " Zhu, Lingshan
2023-08-02 10:00         ` [virtio-comment] " Parav Pandit
2023-08-02 11:35           ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 11:51             ` [virtio-comment] " Parav Pandit
2023-08-02 11:53               ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 11:58                 ` [virtio-comment] " Parav Pandit
2023-08-02 12:10                   ` [virtio-comment] " Michael S. Tsirkin
2023-08-02  8:53 ` [virtio-comment] " Jason Wang
2023-08-02  9:07   ` Parav Pandit
2023-08-02  9:32     ` [virtio-comment] Re: [virtio] " Jason Wang
2023-08-02  9:57       ` [virtio-comment] " Parav Pandit
2023-08-02 11:25         ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 11:29           ` [virtio-comment] " Parav Pandit
2023-08-02 11:39             ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 11:44               ` Parav Pandit
2023-08-02 11:50                 ` Michael S. Tsirkin
2023-08-02 11:56                   ` Parav Pandit
2023-08-02 12:09                     ` Michael S. Tsirkin [this message]
2023-08-03  2:55         ` Jason Wang
2023-08-03 10:13           ` [virtio-comment] " 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=20230802075851-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=hengqi@linux.alibaba.com \
    --cc=jasowang@redhat.com \
    --cc=parav@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio@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