qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
	qemu devel <qemu-devel@nongnu.org>
Cc: zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	weifuqiang <weifuqiang@huawei.com>,
	"eddie . dong" <eddie.dong@intel.com>,
	bian naimeng <biannm@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH V6 02/10] net/filter-mirror.c: Make filter mirror support vnet support.
Date: Thu, 15 Jun 2017 12:31:30 +0800	[thread overview]
Message-ID: <2b200cad-ac3a-fa86-0fa4-cc4dc39b2e09@redhat.com> (raw)
In-Reply-To: <5eff3578-61ac-f41a-1cab-9cc6ef40d7db@cn.fujitsu.com>



On 2017年06月14日 16:04, Zhang Chen wrote:
>
>
> On 06/13/2017 05:14 PM, Jason Wang wrote:
>>
>>
>> On 2017年06月12日 17:27, Zhang Chen wrote:
>>>>
>>>>> +        if (nf->direction == NET_FILTER_DIRECTION_RX ||
>>>>> +            nf->direction == NET_FILTER_DIRECTION_ALL) {
>>>>> +            vnet_hdr_len = nf->netdev->vnet_hdr_len;
>>>>
>>>> This can only work if e.g virtio-net set its own vnet_hdr_len. But 
>>>> looks like it use guest_hdr_len instead.
>>>
>>> I see in hw/net/virtio-net.c use the 
>>> "qemu_set_vnet_hdr_len(nc->peer, n->guest_hdr_len);" to
>>> set the nf->netdev->vnet_hdr_len, any case not include here? 
>>
>> You mean:
>>
>>         if (peer_has_vnet_hdr(n) &&
>>             qemu_has_vnet_hdr_len(nc->peer, n->guest_hdr_len)) {
>>             qemu_set_vnet_hdr_len(nc->peer, n->guest_hdr_len);
>>             n->host_hdr_len = n->guest_hdr_len;
>>         }
>>
>> ?
>>
>> From the code, it only set peer's vnet header when peer supports 
>> vnet_hdr up to n->guest_hdr_len. If peer can't, virtio-net will strip 
>> the header.
>
> So, We should get the n->guest_hdr_len in another way? like set a new 
> parameter in NetClientState?
> Any suggestion about it?
>
> Thanks
> Zhang Chen

Rethink about this, a question is do we really care guest vnet header 
len? During guest transmission, when packet reaches netfilter. The 
vnet_header should have been stripped to netdev->vnet_hdr_len.

I still think use nf->netdev->vnet_hdr_len is sufficient.

Thanks

>
>>
>> Thanks
>>
>>
>>
>

  reply	other threads:[~2017-06-15  4:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07  9:55 [Qemu-devel] [PATCH V6 00/10] Add COLO-proxy virtio-net support Zhang Chen
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 01/10] net: Add vnet_hdr_len arguments in NetClientState Zhang Chen
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 02/10] net/filter-mirror.c: Make filter mirror support vnet support Zhang Chen
2017-06-09  6:08   ` Jason Wang
2017-06-12  9:27     ` Zhang Chen
2017-06-13  9:14       ` Jason Wang
2017-06-14  8:04         ` Zhang Chen
2017-06-15  4:31           ` Jason Wang [this message]
2017-06-15  8:10             ` Zhang Chen
2017-06-16  2:17               ` Jason Wang
2017-06-16  8:36                 ` Zhang Chen
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 03/10] net/filter-mirror.c: Add new option to enable vnet support for filter-redirector Zhang Chen
2017-06-09  6:09   ` Jason Wang
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 04/10] net/net.c: Add vnet_hdr support in SocketReadState Zhang Chen
2017-06-09  6:15   ` Jason Wang
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 05/10] net/colo.c: Make vnet_hdr_len as packet property Zhang Chen
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 06/10] net/colo-compare.c: Make colo-compare support vnet_hdr_len Zhang Chen
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 07/10] net/colo.c: Add vnet packet parse feature in colo-proxy Zhang Chen
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 08/10] net/colo-compare.c: Add vnet packet's tcp/udp/icmp compare Zhang Chen
2017-06-09  6:17   ` Jason Wang
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 09/10] net/filter-rewriter.c: Make filter-rewriter support vnet_hdr_len Zhang Chen
2017-06-09  6:20   ` Jason Wang
2017-06-07  9:55 ` [Qemu-devel] [PATCH V6 10/10] docs/colo-proxy.txt: Update colo-proxy usage of net driver with vnet_header Zhang Chen
2017-06-09  6:22   ` 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=2b200cad-ac3a-fa86-0fa4-cc4dc39b2e09@redhat.com \
    --to=jasowang@redhat.com \
    --cc=biannm@cn.fujitsu.com \
    --cc=eddie.dong@intel.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weifuqiang@huawei.com \
    --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).