From: Jason Wang <jasowang@redhat.com> To: Guo Zhi <qtxuning1999@sjtu.edu.cn> Cc: eperezma <eperezma@redhat.com>, Stefano Garzarella <sgarzare@redhat.com>, mst <mst@redhat.com>, netdev <netdev@vger.kernel.org>, linux-kernel <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>, virtualization <virtualization@lists.linux-foundation.org> Subject: Re: [RFC 0/5] In virtio-spec 1.1, new feature bit VIRTIO_F_IN_ORDER was introduced. Date: Thu, 21 Jul 2022 17:17:13 +0800 [thread overview] Message-ID: <CACGkMEtvjy1_NYHOV=VKMWcggYnOUBk3PRue=t0Kd4wtHjfzQg@mail.gmail.com> (raw) In-Reply-To: <20220721084341.24183-1-qtxuning1999@sjtu.edu.cn> On Thu, Jul 21, 2022 at 4:44 PM Guo Zhi <qtxuning1999@sjtu.edu.cn> wrote: > > When this feature has been negotiated, virtio driver will use > descriptors in ring order: starting from offset 0 in the table, and > wrapping around at the end of the table. Vhost devices will always use > descriptors in the same order in which they have been made available. > This can reduce virtio accesses to used ring. > > Based on updated virtio-spec, this series realized IN_ORDER prototype > in virtio driver and vhost. Thanks a lot for the series. I wonder if you can share any performance numbers for this? Thanks > > Guo Zhi (5): > vhost: reorder used descriptors in a batch > vhost: announce VIRTIO_F_IN_ORDER support > vhost_test: batch used buffer > virtio: get desc id in order > virtio: annouce VIRTIO_F_IN_ORDER support > > drivers/vhost/test.c | 15 +++++++++++- > drivers/vhost/vhost.c | 44 ++++++++++++++++++++++++++++++++++-- > drivers/vhost/vhost.h | 4 ++++ > drivers/virtio/virtio_ring.c | 39 +++++++++++++++++++++++++------- > 4 files changed, 91 insertions(+), 11 deletions(-) > > -- > 2.17.1 >
WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com> To: Guo Zhi <qtxuning1999@sjtu.edu.cn> Cc: kvm <kvm@vger.kernel.org>, mst <mst@redhat.com>, netdev <netdev@vger.kernel.org>, linux-kernel <linux-kernel@vger.kernel.org>, virtualization <virtualization@lists.linux-foundation.org>, eperezma <eperezma@redhat.com> Subject: Re: [RFC 0/5] In virtio-spec 1.1, new feature bit VIRTIO_F_IN_ORDER was introduced. Date: Thu, 21 Jul 2022 17:17:13 +0800 [thread overview] Message-ID: <CACGkMEtvjy1_NYHOV=VKMWcggYnOUBk3PRue=t0Kd4wtHjfzQg@mail.gmail.com> (raw) In-Reply-To: <20220721084341.24183-1-qtxuning1999@sjtu.edu.cn> On Thu, Jul 21, 2022 at 4:44 PM Guo Zhi <qtxuning1999@sjtu.edu.cn> wrote: > > When this feature has been negotiated, virtio driver will use > descriptors in ring order: starting from offset 0 in the table, and > wrapping around at the end of the table. Vhost devices will always use > descriptors in the same order in which they have been made available. > This can reduce virtio accesses to used ring. > > Based on updated virtio-spec, this series realized IN_ORDER prototype > in virtio driver and vhost. Thanks a lot for the series. I wonder if you can share any performance numbers for this? Thanks > > Guo Zhi (5): > vhost: reorder used descriptors in a batch > vhost: announce VIRTIO_F_IN_ORDER support > vhost_test: batch used buffer > virtio: get desc id in order > virtio: annouce VIRTIO_F_IN_ORDER support > > drivers/vhost/test.c | 15 +++++++++++- > drivers/vhost/vhost.c | 44 ++++++++++++++++++++++++++++++++++-- > drivers/vhost/vhost.h | 4 ++++ > drivers/virtio/virtio_ring.c | 39 +++++++++++++++++++++++++------- > 4 files changed, 91 insertions(+), 11 deletions(-) > > -- > 2.17.1 > _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-07-21 9:17 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-21 8:43 [RFC 0/5] In virtio-spec 1.1, new feature bit VIRTIO_F_IN_ORDER was introduced Guo Zhi 2022-07-21 8:43 ` [RFC 1/5] vhost: reorder used descriptors in a batch Guo Zhi 2022-07-22 7:07 ` Eugenio Perez Martin 2022-08-02 3:30 ` Guo Zhi 2022-07-26 7:36 ` Jason Wang 2022-07-26 7:36 ` Jason Wang [not found] ` <2a8838c4-2e6f-6de7-dcdc-572699ff3dc9@sjtu.edu.cn> 2022-07-29 7:32 ` Jason Wang 2022-07-29 7:32 ` Jason Wang 2022-08-02 3:09 ` Guo Zhi 2022-08-02 14:12 ` Guo Zhi 2022-08-04 5:04 ` Jason Wang 2022-08-04 5:04 ` Jason Wang 2022-08-11 8:58 ` Guo Zhi 2022-08-02 13:54 ` Guo Zhi 2022-07-21 8:43 ` [RFC 2/5] vhost: announce VIRTIO_F_IN_ORDER support Guo Zhi 2022-07-21 8:43 ` [RFC 3/5] vhost_test: batch used buffer Guo Zhi 2022-07-22 7:12 ` Eugenio Perez Martin 2022-08-02 2:47 ` Guo Zhi 2022-08-02 3:08 ` Guo Zhi [not found] ` <1D1ABF88-B503-4BE0-AC83-3326EAA62510@sjtu.edu.cn> 2022-08-02 7:45 ` Stefano Garzarella 2022-08-02 7:45 ` Stefano Garzarella 2022-07-21 8:43 ` [RFC 4/5] virtio: get desc id in order Guo Zhi 2022-07-26 8:07 ` Jason Wang 2022-07-26 8:07 ` Jason Wang 2022-07-28 8:12 ` Guo Zhi 2022-08-11 8:49 ` Guo Zhi 2022-07-21 8:43 ` [RFC 5/5] virtio: annouce VIRTIO_F_IN_ORDER support Guo Zhi 2022-07-21 9:17 ` Jason Wang [this message] 2022-07-21 9:17 ` [RFC 0/5] In virtio-spec 1.1, new feature bit VIRTIO_F_IN_ORDER was introduced Jason Wang 2022-07-21 11:54 ` Guo Zhi
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='CACGkMEtvjy1_NYHOV=VKMWcggYnOUBk3PRue=t0Kd4wtHjfzQg@mail.gmail.com' \ --to=jasowang@redhat.com \ --cc=eperezma@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mst@redhat.com \ --cc=netdev@vger.kernel.org \ --cc=qtxuning1999@sjtu.edu.cn \ --cc=sgarzare@redhat.com \ --cc=virtualization@lists.linux-foundation.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.