From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: victork@redhat.com, yvugenfi@redhat.com, qemu-devel@nongnu.org,
wexu@redhat.com, marcel@redhat.com, dfleytma@redhat.com
Subject: Re: [Qemu-devel] [ RFC Patch v5 0/2] Support Receive-Segment-Offload(RSC) for WHQL
Date: Wed, 25 May 2016 16:08:50 +0800 [thread overview]
Message-ID: <57455D92.3080008@redhat.com> (raw)
In-Reply-To: <20160524112527-mutt-send-email-mst@redhat.com>
On 2016年05月24日 16:26, Michael S. Tsirkin wrote:
> On Tue, May 24, 2016 at 04:03:04PM +0800, Jason Wang wrote:
>> >
>> >
>> >On 2016年05月24日 04:14,wexu@redhat.com wrote:
>>> > >From: Wei Xu<wexu@redhat.com>
>>> > >
>>> > >Changes in V5:
>>> > >- Passed all IPv4/6 test cases
>>> > >- Add new fields in 'virtio_net_hdr'
>>> > >- Set 'gso_type' & 'coalesced packets' in new field.
>>> > >- Bypass all 'tcp option' packet
>>> > >- Bypass all 'pure ack' packet
>>> > >- Bypass all 'duplicate ack' packet
>>> > >- Change 'guest_rsc' feature bit to 'false' by default
>>> > >- Feedbacks from v4, typo, etc.
>> >
>> >Patch does not apply on master ...
>> >
>>> > >
>>> > >Note:
>>> > >There is still a few pending issues about the feature bit, and need to be
>>> > >discussed with windows driver maintainer, so linux guests with this patch
>>> > >won't work at current, haven't figure it out yet, but i'm guessing it's
>>> > >caused by the 'gso_type' is set to 'VIRTIO_NET_HDR_GSO_TCPV4/6',
>>> > >will fix it after get the final solution, the below test steps and
>>> > >performance data is based on v4.
>> >
>> >Can we split the patches into smaller ones to make review or merging easier?
>> >E.g can we send the patches without any feature negotiation and vnet header
>> >extension?
>> >
>> >We can focus on the coalescing (maybe ipv4) without any guest involvement in
>> >this series. In this way, the issues were limited and can be converged soon.
>> >After this has been merged, we can add patches that co-operate with guests
>> >on top (since it needs agreement on virtio specs). Does this sounds a good
>> >plan?
> True but disabling everything when feature is not negotiated
> reduces the risk somewhat.
>
Yes, but I believe we can only merge the patch with new virtio features
after they were accepted by spec?
next prev parent reply other threads:[~2016-05-25 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 20:14 [Qemu-devel] [ RFC Patch v5 0/2] Support Receive-Segment-Offload(RSC) for WHQL wexu
2016-05-23 20:14 ` [Qemu-devel] [ RFC Patch v5 1/2] virtio-net rsc: support coalescing ipv4 tcp traffic wexu
2016-05-24 8:33 ` [Qemu-devel] [ RFC Patch v5 1/2] virtio-net rsc: support coalescing ipv4 tcp traffic/ Michael S. Tsirkin
2016-05-23 20:14 ` [Qemu-devel] [ RFC Patch v5 2/2] virtio-net rsc: support coalescing ipv6 tcp traffic wexu
2016-05-24 8:03 ` [Qemu-devel] [ RFC Patch v5 0/2] Support Receive-Segment-Offload(RSC) for WHQL Jason Wang
2016-05-24 8:26 ` Michael S. Tsirkin
2016-05-24 9:49 ` Wei Xu
2016-05-25 8:08 ` Jason Wang [this message]
2016-05-25 8:26 ` Michael S. Tsirkin
2016-05-24 9:49 ` Wei Xu
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=57455D92.3080008@redhat.com \
--to=jasowang@redhat.com \
--cc=dfleytma@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=victork@redhat.com \
--cc=wexu@redhat.com \
--cc=yvugenfi@redhat.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 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.