From: Jason Wang <jasowang@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Yang Hongyang <hongyang.yang@easystack.cn>,
"eddie . dong" <eddie.dong@intel.com>,
qemu devel <qemu-devel@nongnu.org>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: Re: [Qemu-devel] [RFC PATCH 3/3] filter-rewriter: rewrite tcp packet to keep secondary connection
Date: Wed, 29 Jun 2016 09:55:03 +0800 [thread overview]
Message-ID: <57732A77.1050209@redhat.com> (raw)
In-Reply-To: <57721A55.8020906@cn.fujitsu.com>
On 2016年06月28日 14:33, Zhang Chen wrote:
>>>
>>>>
>>>>> primary guest response
>>>>> pkt(seq=primary_seq+1,ack=client_seq+1+data_len,flag=ACK)
>>>>> secondary guest response
>>>>> pkt(seq=secondary_seq+1,ack=client_seq+1+data_len,flag=ACK)
>>>>
>>>> Is ACK a must here?
>>>
>>> Yes.
>>>
>>
>> Looks not, e.g what happens if guest does not use piggybacking acks?
>>
>>
>
> If guest does not use piggybacking acks, it will send a independent
> packet for ack.
> we will get this packet.
> like:
> pkt(seq=xxxx,ack=xxx,flag=ACK).
Right, so looks like if guest want to send some data too, it can send
tcp packet without ACK set?
next prev parent reply other threads:[~2016-06-29 1:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 11:15 [Qemu-devel] [RFC PATCH 0/3] filter-rewriter: introduce filter-rewriter Zhang Chen
2016-06-14 11:15 ` [Qemu-devel] [RFC PATCH 1/3] filter-rewriter: introduce filter-rewriter initialization Zhang Chen
2016-06-14 11:15 ` [Qemu-devel] [RFC PATCH 2/3] filter-rewriter: track connection and parse packet Zhang Chen
2016-06-14 11:15 ` [Qemu-devel] [RFC PATCH 3/3] filter-rewriter: rewrite tcp packet to keep secondary connection Zhang Chen
2016-06-20 6:27 ` Jason Wang
2016-06-20 12:14 ` Dr. David Alan Gilbert
2016-06-22 3:12 ` Zhang Chen
2016-06-22 6:34 ` Jason Wang
2016-06-23 10:48 ` Zhang Chen
2016-06-24 6:08 ` Jason Wang
2016-06-28 6:33 ` Zhang Chen
2016-06-29 1:55 ` Jason Wang [this message]
2016-06-29 6:13 ` Zhang Chen
2016-06-30 12:17 ` Jason Wang
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=57732A77.1050209@redhat.com \
--to=jasowang@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=hongyang.yang@easystack.cn \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.com \
--cc=zhangchen.fnst@cn.fujitsu.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).