qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rick Zhong <zhaoyong.zhong@nephogine.com>
Cc: Eugenio Perez Martin <eperezma@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Jason Wang <jasowang@redhat.com>, Peter Xu <peterx@redhat.com>,
	Guo Zhi <qtxuning1999@sjtu.edu.cn>,
	Xinying Yu <xinying.yu@nephogine.com>,
	Wentao Jia <wentao.jia@nephogine.com>,
	Shujing Dong <shujing.dong@nephogine.com>,
	Kyle Xu <zhenbing.xu@nephogine.com>
Subject: Re: 回复: FW: [PATCH] vhost-user: add VIRTIO_F_IN_ORDER and VIRTIO_F_NOTIFICATION_DATA feature
Date: Tue, 13 Feb 2024 04:52:49 -0500	[thread overview]
Message-ID: <20240213044703-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DM6PR13MB39889A667DB46A0EC65FA08495422@DM6PR13MB3988.namprd13.prod.outlook.com>

On Fri, Feb 02, 2024 at 10:27:33AM +0000, Rick Zhong wrote:
> Hi Eugenio and Michael,
> 
> Let me make it more clear about the target for this patch. Currently Corigine is developing the vDPA features on NIC which are based on the QEMU vhost-vdpa/vhost-user backend. These two virtio features are helpful in data plane performance.
> 
> In my understanding, these two virtio features are defined as part of the basic facilities of a common virtio device, which means they can be utilized by virtio-net, virtio-blk, virtio-fs... whatever backend. To implement, it is beyond the team's knowledge to handle these for all kinds of backends. So I'd prefer to set them off by default and raise an warning for other type of backends, except vhost-vdpa/vhost-user.
> 
> Best Regards,
> Rick Zhong

Yes, you should set it off by default.  No, just skipping implementation
won't cut it.  It is understandable that you just want your own use-case
addressed and it is annoying to get roped in to do some work on qemu.
However, such is the cost of doing this business.  If instead we add
hacks like the warning you mention then the codebase quickly becomes a
mess of special cases.  If you need this feature, you have to make it
nicely orthogonal and palatable to everyone. It is really not a lot
of coding work, mostly testing.

-- 
MST



  reply	other threads:[~2024-02-13  9:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 10:11 [PATCH] vhost-user: add VIRTIO_F_IN_ORDER and VIRTIO_F_NOTIFICATION_DATA feature Wentao Jia
     [not found] ` <SN4PR13MB5727D7B4E7CC91345135A5058661A@SN4PR13MB5727.namprd13.prod.outlook.com>
     [not found]   ` <CACGkMEvwanHfheCMo-gDjzx1DrX51AMtoaYJ9PcE0yYmZdA+Uw@mail.gmail.com>
     [not found]     ` <SN4PR13MB5727A90B141E383127F1E25D8661A@SN4PR13MB5727.namprd13.prod.outlook.com>
2024-01-02  5:56       ` FW: " Wentao Jia
2024-01-12  8:18         ` Wentao Jia
2024-01-15  0:18           ` Jason Wang
2024-01-16  1:57             ` Wentao Jia
2024-01-16  2:20               ` Jason Wang
2024-01-16  6:38                 ` Wentao Jia
2024-01-19  6:35                   ` Wentao Jia
2024-01-19 10:26                     ` Eugenio Perez Martin
2024-01-19 10:39                       ` 回复: " Rick Zhong
2024-01-26  8:58                         ` Wentao Jia
2024-01-26 18:04                           ` Eugenio Perez Martin
2024-02-01 10:47                             ` Wentao Jia
2024-02-01 12:01                               ` Eugenio Perez Martin
2024-02-01 12:58                               ` Michael S. Tsirkin
2024-02-02 10:27                                 ` 回复: " Rick Zhong
2024-02-13  9:52                                   ` Michael S. Tsirkin [this message]
2024-02-18  1:55                                     ` 回复: " Rick Zhong

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=20240213044703-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qtxuning1999@sjtu.edu.cn \
    --cc=shujing.dong@nephogine.com \
    --cc=wentao.jia@nephogine.com \
    --cc=xinying.yu@nephogine.com \
    --cc=zhaoyong.zhong@nephogine.com \
    --cc=zhenbing.xu@nephogine.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;
as well as URLs for NNTP newsgroup(s).