From: Wei Xu <wexu@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, jasowang@redhat.com, jfreiman@redhat.com,
maxime.coquelin@redhat.com, tiwei.bie@intel.com
Subject: Re: [Qemu-devel] [PATCH v3 00/11] packed ring virtio-net backends support
Date: Thu, 14 Feb 2019 11:52:18 +0800 [thread overview]
Message-ID: <20190214035218.GA12997@wei-ubt> (raw)
In-Reply-To: <20190213091402-mutt-send-email-mst@kernel.org>
On Wed, Feb 13, 2019 at 09:17:57AM -0500, Michael S. Tsirkin wrote:
> On Wed, Feb 13, 2019 at 08:25:35AM -0500, wexu@redhat.com wrote:
> > From: Wei Xu <wexu@redhat.com>
> >
> > https://github.com/Whishay/qemu.git
> >
> > Userspace and vhost-net backedn test has been done with upstream kernel
> > in guest.
>
> Just a general comment: please format *all* patches
> with --subject-prefix "PATCH v3", or with -v3.
>
> Do not manually change patch 0 subject adding version there.
>
> This makes it possible to figure out where does each patch go.
>
OK, thanks a lot.
Wei
>
> > v2->v3
> > v2/01 - drop it since the header has been synchronized from kernel.(mst & jason)
> > v3/01 - rename 'avail_wrap_counter' to 'last_avail_wrap_counter',
> > 'event_wrap_counter' to 'avail_wrap_counter' to make it easier
> > to understand.(Jason)
> > - revise commit message.(Jason)
> > v3/02 - split packed ring areas size calculation to next patch.(Jason)
> > to not break bisect(Jason).
> > v3/03 - initialize packed ring region with correct size and attribute.
> > - remove unnecessary 'else' checks. (Jason)
> > v3/06 - add commit log.
> > - replace 'event_wrap-counter' with 'avail_wrap_counter'.
> > - merge common memory cache size check to virtqueue_get_avail_bytes().(Jason)
> > - revise memory barrier comment.(Jason)
> > - check indirect descriptors by desc.len/sizeof(desc).(Jason)
> > - flip wrap counter with '^=1'.(Jason)
> > v3/07 - move desc.id/len initialization to the declaration.(Jason)
> > - flip wrap counter '!' with '^=1'.(Jason)
> > - add memory barrier comments in commit message.
> > v3/08 - use offsetof() when writing cache.(Jason)
> > - avoid duplicated memory region write when turning off event_idx
> > supported notification.(Jason)
> > - add commit log.(Jason)
> > - add avail & last_avail wrap counter difference description in commit log.
> > v3/09 - remove unnecessary used/avail idx/wrap-counter from subsection.
> > - put new subsection to the end of vmstate_virtio.(Jason)
> > - squash the two userspace and vhost-net migration patches in v2.(Jason)
> > v3/10 - reword commit message.
> > - this is a help not a bug fix so I would like to keep it as a
> > separate patch still.(Proposed a merge it by Jason)
> > - the virtqueue_fill() is also not like an API so I would prefer not
> > to touch it, please correct me if I did not get it in the right
> > way.(Proposed a squash by Jason)
> > v3/11 - squash feature bits for user space and vhost kernel/user backends.
> > - enable packed ring feature bit provision on host by default.(Jason)
> >
> > Wei Xu (11):
> > virtio: rename structure for packed ring
> > virtio: device/driver area size calculation helper for split ring
> > virtio: initialize packed ring region
> > virtio: initialize wrap counter for packed ring
> > virtio: queue/descriptor check helpers for packed ring
> > virtio: get avail bytes check for packed ring
> > virtio: fill/flush/pop for packed ring
> > virtio: event suppression support for packed ring
> > virtio-net: update the head descriptor in a chain lastly
> > virtio: migration support for packed ring
> > virtio: CLI and provide packed ring feature bit by default
> >
> > hw/net/vhost_net.c | 2 +
> > hw/net/virtio-net.c | 11 +-
> > hw/virtio/virtio.c | 798 +++++++++++++++++++++++++++++++++++++++++----
> > include/hw/virtio/virtio.h | 4 +-
> > 4 files changed, 757 insertions(+), 58 deletions(-)
> >
> > --
> > 1.8.3.1
prev parent reply other threads:[~2019-02-14 3:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 13:25 [Qemu-devel] [PATCH v3 00/11] packed ring virtio-net backends support wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 01/11] virtio: rename structure for packed ring wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 02/11] virtio: device/driver area size calculation helper for split ring wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 03/11] virtio: initialize packed ring region wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 04/11] virtio: initialize wrap counter for packed ring wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 05/11] virtio: queue/descriptor check helpers " wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 06/11] virtio: get avail bytes check " wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 07/11] virtio: fill/flush/pop " wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 08/11] virtio: event suppression support " wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 09/11] virtio-net: update the head descriptor in a chain lastly wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 10/11] virtio: migration support for packed ring wexu
2019-02-13 13:25 ` [Qemu-devel] [PATCH 11/11] virtio: CLI and provide packed ring feature bit by default wexu
2019-02-13 14:17 ` [Qemu-devel] [PATCH v3 00/11] packed ring virtio-net backends support Michael S. Tsirkin
2019-02-14 3:52 ` Wei Xu [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=20190214035218.GA12997@wei-ubt \
--to=wexu@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreiman@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tiwei.bie@intel.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).