Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-03-13 Thread LIU Yulong via discuss
Hi Eelco, Thank you. Patch sent to the mail list: https://mail.openvswitch.org/pipermail/ovs-dev/2024-March/412474.html On Wed, Mar 13, 2024 at 5:34 PM Eelco Chaudron wrote: > > > > On 13 Mar 2024, at 10:19, LIU Yulong wrote: > > > Hi guys, > > > > Send

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-03-13 Thread LIU Yulong via discuss
Hi guys, Send a pull request with that try_lock movement fix based on the former tests: https://github.com/openvswitch/ovs/pull/421 Does that make sense to you? Thank you. LIU Yulong On Tue, Mar 12, 2024 at 3:11 PM LIU Yulong wrote: > > Updates: > > Ukey attributes we

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-03-12 Thread LIU Yulong via discuss
tostack/ovs/commit/2919a242be7d0ee079c278a8488188694f20f827 No more core was seen during that revalidator_sweep__ procedure for 4 days now. But if I revert this lock movement, the core can show again in a few hours. So, please take a look at this lock movement patch, if it make sense to you. Regards, LIU Yulo

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-03-01 Thread LIU Yulong via discuss
89 ipf_clean6 100890 hw_offload3 100891 handler4 100892 revalidator5 # 1 revalidator thread 100893 pmd-c03/id:9 100894 pmd-c35/id:8 # Mostly 1 PMD thread is working! Another is idle forever. 100925 vhost_reconn 100926 vhost-events So, this can prove that there are two threads were tryin

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-02-27 Thread LIU Yulong via discuss
: https://github.com/openvswitch/ovs/blob/master/ofproto/ofproto-dpif-upcall.c#L1777 Right? If it is true, I will update the buffer structure, and a counter_upcall_ukey_allocate as well. On Tue, Feb 27, 2024 at 3:34 PM Eelco Chaudron wrote: > > > > On 27 Feb 2024, at 4:44, LIU

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-02-26 Thread LIU Yulong via discuss
;upcall_ukey_free", count = 0x5622b41047f0 , total = 79785, last_total = 79785, min = {0, 0, 0, 0, 0, 55, 22681, 11703, 13877, 12750, 0, 18719}, hr = {79785, 0 }} Let's see how this goes. Thank you. On Tue, Feb 27, 2024 at 9:05 AM LIU Yulong wrote: > > @Ilya, thank you, I will add that p

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-02-26 Thread LIU Yulong via discuss
@Ilya, thank you, I will add that patch. @Eelco, thank you again, I will add a RL log to the free(ukey). Hope we can get something useful. On Mon, Feb 26, 2024 at 7:55 PM Ilya Maximets wrote: > > On 2/26/24 11:20, Eelco Chaudron wrote: > > > > > > On 26 Feb 2024, at

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-02-26 Thread LIU Yulong via discuss
] https://github.com/openvswitch/ovs/blob/v2.17.8/ofproto/ofproto-dpif-upcall.c#L2084 For last mail, can this issue be concurrent read-and-update/delete? The revalidator_sweep__ is trying to lock the ukey->mutex, while another thread is updating the ukey->mutex to NULL and free ukey. LIU

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-02-26 Thread LIU Yulong via discuss
ock(>mutex)) { <-- Core at here, because of the NULL pointer. [8] continue; } [8] https://github.com/openvswitch/ovs/blob/v2.17.8/ofproto/ofproto-dpif-upcall.c#L2900 CMIIW, if this race condition can happen, IMO, it is mostly because the umap is not locked during th

Re: [ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-02-20 Thread LIU Yulong via discuss
evalidator (arg=0x562777897b00) at ofproto/ofproto-dpif-upcall.c:1086 #9 0x562773df805f in ovsthread_wrapper (aux_=) at lib/ovs-thread.c:422 #10 0x7fd344480e65 in start_thread (arg=0x7fd334307700) at pthread_create.c:307 #11 0x7fd34260988d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:1

[ovs-discuss] ovs-vswitchd core at revalidator_sweep__

2024-02-19 Thread LIU Yulong via discuss
0x0, __next = 0x0 } }, __size = '\000' , "\377\377\377\377", '\000' , __align = 0 }, where = 0x0 }, ... } There seems to be an out-of-bounds access to the linked list of ukeys here. So, I would greatly appreciate your help, as it is crucial for OVS to operate in our production environment. I can provide further debug related output information at any time. Waiting for your response... Thank you very much in advance. Best regards, LIU Yulong ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] [ovs-vswitchd] core dump of ovs-vswitchd during revalidator sweep

2023-08-07 Thread LIU Yulong via discuss
g/pipermail/ovs-dev/2016-August/322125.html May I ask if everyone can provide a preliminary evaluation of the problem? How could this happen? And what can we do to work around the problem? Regards, LIU Yulong ___ discuss mailing list disc...@openvswit

[ovs-discuss] [HOW TO] get switch port information by openvswitch lldp

2023-04-24 Thread LIU Yulong via discuss
: Router, on Port: PortID: ifname 10GE1/0/11 PortDescr:TO_ TTL: 120 Thanks. LIU Yulong ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] How to add multiple resubmit(, table) actions to one flow for OPENFLOW13 and upper?

2022-08-02 Thread LIU Yulong
MOD message Ryu controller instructions are: instructions = [ ofpp.OFPInstructionActions(ofp.OFPIT_APPLY_ACTIONS, actions), ofpp.OFPInstructionGotoTable(table_id=table1), ofpp.OFPInstructionGotoTable(table_id=table2)] Is this possible? Or am I missing something?

Re: [ovs-discuss] Action "mod_nw_tos:" for OPENFLOW13

2021-07-12 Thread LIU Yulong
t;ip_dscp,load:0x37->NXM_NX_REG2[0..5],resubmit(,0) """ On Tue, Jul 13, 2021 at 12:14 AM Ben Pfaff wrote: > > On Mon, Jul 12, 2021 at 03:13:13PM +0800, LIU Yulong wrote: > > Recently, I tested OpenStack Neutron with DSCP marking functions. But, I > > met so

[ovs-discuss] Action "mod_nw_tos:" for OPENFLOW13

2021-07-12 Thread LIU Yulong
quot; Action "mod_nw_tos:" is causing the error here. So, I would ask which action for OPENFLOW13 is to do same work of "mod_nw_tos:" for OPENFLOW10? These is no doc mentioned such action for OPENFLOW13. Regards, LIU Yulong ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Fwd: [ovs-dpdk] bandwidth issue of vhostuserclient virtio ovs-dpdk

2018-12-03 Thread LIU Yulong
On Sat, Dec 1, 2018 at 1:17 AM LIU Yulong wrote: > > > On Fri, Nov 30, 2018 at 5:36 PM Lam, Tiago wrote: > >> On 30/11/2018 02:07, LIU Yulong wrote: >> > Hi, >> > >> > Thanks for the reply, please see my inline comments below. >> >

Re: [ovs-discuss] Fwd: [ovs-dpdk] bandwidth issue of vhostuserclient virtio ovs-dpdk

2018-11-30 Thread LIU Yulong
On Fri, Nov 30, 2018 at 5:36 PM Lam, Tiago wrote: > On 30/11/2018 02:07, LIU Yulong wrote: > > Hi, > > > > Thanks for the reply, please see my inline comments below. > > > > > > On Thu, Nov 29, 2018 at 6:00 PM Lam, Tiago > <mailto:tiago@intel

[ovs-discuss] Fwd: [ovs-dpdk] bandwidth issue of vhostuserclient virtio ovs-dpdk

2018-11-29 Thread LIU Yulong
Hi, Thanks for the reply, please see my inline comments below. On Thu, Nov 29, 2018 at 6:00 PM Lam, Tiago wrote: > On 29/11/2018 08:24, LIU Yulong wrote: > > Hi, > > > > We recently tested ovs-dpdk, but we met some bandwidth issue. The > bandwidth > &g

[ovs-discuss] [ovs-dpdk] bandwidth issue of vhostuserclient virtio ovs-dpdk

2018-11-29 Thread LIU Yulong
: 232 HugePages_Free: 10 HugePages_Rsvd:0 HugePages_Surp:0 # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.10.0-862.11.6.el7.x86_64 root=UUID=220ee106-5e00-4809-91a0-641e045a4c21 ro intel_idle.max_cstate=0 crashkernel=auto rhgb quiet default_hugepagesz=1G hugepagesz=1G hugepages=232 iommu=pt intel_iommu=on Best regards, LIU Yulong ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel 3.10.0-514.2.2.el7.x86_64)

2017-01-11 Thread LIU Yulong
itch/ovs/commit/6ccf21ca77ec092aa6 > 3b3daff66dc9f0d0e1be93 > > On 11/01/2017 18:14, "liu yulong" <liuyulong...@gmail.com> wrote: > > Thanks Joe and Ben, actually the master branch we also got such error. > The doc we followed is "Fedora, RHEL 7.x Packaging for Open vSwi

[ovs-discuss] Failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel 3.10.0-514.2.2.el7.x86_64)

2017-01-11 Thread liu yulong
Hi experts, We have failed to build Open vSwitch Kernel Modules on CentOS 7 (kernel 3.10.0-514.2.2.el7.x86_64). Here are some traces we got: http://paste.openstack.org/show/594350/ Steps: 1. download the current openvswitch release: http://openvswitch.org/releases/openvswitch-2.6.1.tar.gz 2.