Ok, I got it, thanks for your explanation.
> -Original Message-
> From: Ilya Maximets [mailto:i.maxim...@samsung.com]
> Sent: Monday, February 11, 2019 9:55 PM
> To: Lilijun (Jerry, Cloud Networking) ; Stokes, Ian
> ; d...@openvswitch.org
> Subject: Re: [ovs-dev] dpif
Yes, Thanks for your help again.
Let's forget the patch :). But in my opinion, the function
reload_affected_pmds() doesn't need be locked within dp->port_mutex. Is that
true?
> -Original Message-
> From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev-
> boun...@openvswitch.org] O
Hi all,
Currently, when insert/delete/lookup the shash list struct ofproto‘s
port_by_name, we have no lock to protect this list. This list was used lots of
other functions.
Is there something race issues? Can we make sure it's only used in the main
ovs thread?
Thanks.
__
Maximets [mailto:i.maxim...@samsung.com]
> Sent: Thursday, January 31, 2019 5:12 PM
> To: Lilijun (Jerry, Cloud Networking) ;
> d...@openvswitch.org
> Cc: Stokes, Ian
> Subject: Re: [ovs-dev] dpif-netdev:fix reload pmd's dead lock
>
> Hi.
>
> On 31.01.2019 8:57, Lilijun
Hi all,
I found one branch of OVS in github.com which have not been updated for 4
years.
Are there any plan or work to support P4 in OVS?
Thanks
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
other threads have changed the global_seqno.
> -Original Message-
> From: Ben Pfaff [mailto:b...@ovn.org]
> Sent: Monday, December 10, 2018 11:49 PM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: d...@openvswitch.org
> Subject: Re: [ovs-dev] [PATCH] [PATCH] rcu: reduce RCU
8 AM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: d...@openvswitch.org
> Subject: Re: [ovs-dev] [PATCH] [PATCH] rcu: reduce RCU block time
>
> If that's the case, then there's something wrong with seq_wait() or the use
> of it in this context. The timer logic here is just to
Original Message-
> From: Ben Pfaff [mailto:b...@ovn.org]
> Sent: Friday, December 07, 2018 10:37 PM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: d...@openvswitch.org
> Subject: Re: [ovs-dev] [PATCH] [PATCH] rcu: reduce RCU block time
>
> On Fri, Dec 07, 2018 at 02:03:27PM +08
...@ovn.org]
> Sent: Thursday, December 06, 2018 10:58 PM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: d...@openvswitch.org
> Subject: Re: [ovs-dev] [PATCH] [PATCH] rcu: reduce RCU block time
>
> On Thu, Dec 06, 2018 at 08:28:19PM +0800, Lilijun wrote:
> > When calling ov
VLAN.
-Original Message-
From: Ben Pfaff [mailto:b...@ovn.org]
Sent: Tuesday, September 11, 2018 3:33 AM
To: Eric Garver ; Lilijun (Jerry, Cloud Networking)
; d...@openvswitch.org; ovs-disc...@openvswitch.org
Subject: Re: [ovs-discuss] [PATCH v2] [ovs-dev] [PATCH] QinQ: support more vlan
head
Hi Eric,
Yes, I agree with that effect.
But how about this issue of QinQ that we can only support at most 2 VLANs ? Do
you have any ideas?
Thanks.
-Original Message-
From: Eric Garver [mailto:e...@garver.life]
Sent: Friday, September 07, 2018 10:14 PM
To: Lilijun (Jerry, Cloud
Yes, That's OK, thanks.
-Original Message-
From: Ben Pfaff [mailto:b...@ovn.org]
Sent: Saturday, September 08, 2018 1:59 AM
To: Eric Garver ; d...@openvswitch.org; Lilijun (Jerry, Cloud
Networking)
Subject: Re: [PATCH] vswitch.xml: Better explain vlan-limit.
On Fri, Sep 07, 20
That’s more clear to me.
thanks.
发件人： Ben Pfaff
收件人： Eric
Garvermailto:e...@garver.life>>;devmailto:d...@openvswitch.org>>;Lilijun
(Jerry, Cloud
Networking)mailto:jerry.lili...@huawei.com>>
主题： Re: [PATCH] vswitch.xml: Better explain vlan-limit.
时间： 2018-09-08 01:59:34
On Fr
, September 07, 2018 12:13 PM
To: Lilijun (Jerry, Cloud Networking)
Cc: ovs-disc...@openvswitch.org; d...@openvswitch.org; Eric Garver
Subject: Re: [ovs-discuss] [PATCH] [ovs-dev] [PATCH] QinQ: support more vlan
headers.
On Fri, Sep 07, 2018 at 02:51:25AM +, Lilijun (Jerry, Cloud Networking
In my test, vlan-limit is set to 0 that means unlimited the count of vlan
headers.
ovs-vsctl set Open_vSwitch . other_config:vlan-limit=0
But in fact the macro FLOW_MAX_VLAN_HEADERS is defined as 2, so we can
only support max two vlan headers. It doesn't work as the config vlan-limit's
description
Sorry, I will push it again to fix this error.
-Original Message-
From: Ben Pfaff [mailto:b...@ovn.org]
Sent: Friday, September 07, 2018 12:20 PM
To: Lilijun (Jerry, Cloud Networking)
Cc: ovs-disc...@openvswitch.org; d...@openvswitch.org; Eric Garver
Subject: Re: [ovs-discuss] [PATCH
Hi all,
In my test, vlan-limit is set to 0 that means unlimited the count of vlan
headers.
ovs-vsctl set Open_vSwitch . other_config:vlan-limit=0
But in fact the macro FLOW_MAX_VLAN_HEADERS is defined as 2, so we can
only support max two vlan headers. It doesn't work as the config vlan-limit's
de
OK, Thanks for your reply.
Maybe we need adapt to the change currently if no better something happen.
-Original Message-
From: Eric Garver [mailto:e...@erig.me]
Sent: Thursday, August 23, 2018 3:00 AM
To: Lilijun (Jerry, Cloud Networking)
Cc: wangyunjian ; d...@openvswitch.org
Hi Eric and all,
Thanks for Eric's advice very much.
But in my opinion, this issue reported from wangyunjian is something about
feature's compatibility.
Using the rule: ovs-ofctl -O OpenFlow13 add-flow ovsbr0 "
table=0,priority=2,in_port=1 actions=mod_vlan_vid:3,NORMAL",
the action mod_vlan_
I think this dpdkbond option is worthy of being supported.
In my view, ovs bonding works based on openflow upcall processing. When some
slave gets link down, the datapath flows related it will be flushed an
revalidated.
As a result, that may cause a great deal of upcall requests to be handled a
apath flows.
Is that ok?
Thanks.
-邮件原件-
发件人: Ben Pfaff [mailto:b...@ovn.org]
发送时间: 2018年5月25日 1:13
收件人: Lilijun (Jerry, Cloud Networking)
抄送: d...@openvswitch.org; ovs-disc...@openvswitch.org; liucheng (J)
; lixiao (H)
主题: Re: 答复: Question: why ovs flush all datapath flows
Are there anybody has some ideas about this question?
Thanks.
-邮件原件-
发件人: Lilijun (Jerry, Cloud Networking)
发送时间: 2018年5月18日 11:02
收件人: d...@openvswitch.org; 'Ben Pfaff' ;
ovs-disc...@openvswitch.org
抄送: liucheng (J) ; lixiao (H)
主题: Question: why ovs flush all datapath
Hi all,
In my test, there are many VMs sending and receiving random flows using ovs.
Per VM has one virtio-net NIC and connect to ovs bridge named such as
br-plyXXX. These ovs bridges br-plyXXX are all connected to br-int using patch
port.
All VM's traffic can generate about 200 thousand datapa
What's the megaflow match policy about move:NXM_OF_IP_DST? Why we don't using
megaflow wildcard on the openflow actions of move:NXM_OF_IP_DST[]?
Thank you!
B.R.
Lilijun
-邮件原件-
发件人: Lilijun (Jerry, Cloud Networking)
发送时间: 2018年4月4日 11:56
收件人: d...@openvswitch.org; '
Hi all,
In my test, add one flow to br-ovs, and running one vm connected this br-ovs:
cookie=0x0, duration=286.272s, table=31, n_packets=2, n_bytes=196,
idle_age=161, priority=61010,ip,metadata=0x2b193,dl_dst=00:00:00:04:06:03
actions=move:NXM_OF_IP_DST[]->NXM_NX_REG0[],load:0x8439ce602f->OXM_OF
I have tested your patch and can fix my problem described in the following
patch.
https://mail.openvswitch.org/pipermail/ovs-dev/2018-January/343423.html
Thanks.
-邮件原件-
发件人: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev-boun...@openvswitch.org]
代表 Ben Pfaff
发送时间: 2018年1月25日 1:41
收件人:
Yes, I also found this four related functions just again.
I will do some test with your patch, thanks.
-邮件原件-
发件人: Huanle Han [mailto:hanxue...@gmail.com]
发送时间: 2018年1月23日 12:33
收件人: Ben Pfaff ; Lilijun (Jerry)
抄送: ; Liuyongan
; Zhoujingbin
主题: Re: [ovs-dev] [PATCH] Ofproto: fix
Hi all,
In my test, the new datapath flow which has the same in_port and actions output
port was found using ovs-appctl dpctl/dump-flows.
Then the mac address will move from one port to another and back it again in
the physical switch. This problem result in the VM's traffic become abnormal.
28 matches
Mail list logo
