Re: [ovs-dev] [PATCH v2 2/3] travis: Move x86-only addon packages to linux-prepare.sh
> -Original Message-
> From: Ilya Maximets
> Sent: Saturday, December 14, 2019 1:55 AM
> To: dwilder ; Lance Yang (Arm Technology China)
>
> Cc: ovs-dev@openvswitch.org; i.maxim...@ovn.org; b...@ovn.org; Yanqin Wei (Arm
> Technology China) ; Gavin Hu (Arm Technology China)
> ; Ruifeng Wang (Arm Technology China)
> ;
> Jieqiang Wang (Arm Technology China) ; Malvika Gupta
> ; nd
> Subject: Re: [ovs-dev] [PATCH v2 2/3] travis: Move x86-only addon packages to
> linux-
> prepare.sh
>
> On 06.12.2019 23:32, dwilder wrote:
> > On 2019-12-05 19:26, Lance Yang wrote:
> >> To enable multiple CPU architectures support, it is necessary to move
> >> the x86-only addon packages from .travis.yml file. Otherwise, the
> >> x86-only addon packages will break the builds on some other CPU
> >> architectures.
> >>
> >> Reviewed-by: Yanqin Wei
> >> Reviewed-by: Malvika Gupta
> >> Reviewed-by: Gavin Hu
> >> Reviewed-by: Ruifeng Wang
> >> Signed-off-by: Lance Yang
> >> ---
> >> .travis.yml | 2 --
> >> .travis/linux-prepare.sh | 3 ++-
> >> 2 files changed, 2 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/.travis.yml b/.travis.yml index 482efd2..2dc4d43 100644
> >> --- a/.travis.yml
> >> +++ b/.travis.yml
> >> @@ -14,7 +14,6 @@ addons:
> >>apt:
> >> packages:
> >>- bc
> >> - - gcc-multilib
> >>- libssl-dev
> >>- llvm-dev
> >>- libjemalloc1
> >> @@ -26,7 +25,6 @@ addons:
> >>- libelf-dev
> >>- selinux-policy-dev
> >>- libunbound-dev
> >> - - libunbound-dev:i386
> >>- libunwind-dev
> >>
> >> before_install: ./.travis/${TRAVIS_OS_NAME}-prepare.sh
> >> diff --git a/.travis/linux-prepare.sh b/.travis/linux-prepare.sh
> >> index 9e3ac0d..6421066 100755
> >> --- a/.travis/linux-prepare.sh
> >> +++ b/.travis/linux-prepare.sh
> >> @@ -18,7 +18,8 @@ pip install --user --upgrade docutils
> >> if [ "$M32" ]; then
> >> # 32-bit and 64-bit libunwind can not be installed at the same time.
> >> # This will remove the 64-bit libunwind and install 32-bit version.
> >> -sudo apt-get install -y libunwind-dev:i386
> >> +sudo apt-get install -y \
> >> +libunwind-dev:i386 libunbound-dev:i386 gcc-multilib
> >> fi
> >>
> >> # IPv6 is supported by kernel but disabled in TravisCI images:
> >
> > LGTM:
> > With this patch applied ppc64le simply needs to be include into the matrix.
> > I will submit an updated ppc64le patch to be layered on top of this one.
> >
> > Acked-by: David Wilder
>
> Thanks. First two patches of this series are good even without multiarch
> support so I went
> ahead and applied them (with minor visual/spelling changes) to master. We'll
> need to think
> more about actual enabling of ppc/arm since they are not that stable as we
> would want
> them to be.
>
> Best regards, Ilya Maximets.
[Lance]
Hi Ilya,
Thank you for all the comments. I am glad to that the patches can be merged.
We reported the segment fault issue to Travis CI community. You can see the
threads for segment faults in arm64/ppc64 environment:
https://travis-ci.community/t/segfaults-in-arm64-environment/5617/8
https://travis-ci.community/t/arm64-ppc64le-segfaults/6158
There might be a period of time for the Travis CI community to investigate. We
will keep you updated about the latest process.
Best regards, Lance
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH v2 3/3] travis: Enable OvS Travis CI for arm
> -Original Message- > From: Ilya Maximets > Sent: Saturday, December 7, 2019 12:39 AM > To: Lance Yang (Arm Technology China) ; > ovs-dev@openvswitch.org > Cc: i.maxim...@ovn.org; b...@ovn.org; Yanqin Wei (Arm Technology China) > ; dwil...@us.ibm.com; Gavin Hu (Arm Technology China) > ; Ruifeng Wang (Arm Technology China) > ; > Jieqiang Wang (Arm Technology China) ; Malvika Gupta > ; nd > Subject: Re: [ovs-dev] [PATCH v2 3/3] travis: Enable OvS Travis CI for arm > > On 06.12.2019 04:26, Lance Yang wrote: > > Enable part of travis jobs with gcc compiler for arm64 architecture > > > > 1. Add arm jobs into the matrix in .travis.yml configuration file 2. > > To enable OVS-DPDK jobs, set the build target according to different > > CPU architectures 3. Temporarily disable sparse checker because of > > static code checking failure on arm64 > > > > Successful travis build jobs report: > > https://travis-ci.org/yzyuestc/ovs/builds/621037339 > > > > Reviewed-by: Yanqin Wei > > Reviewed-by: Jieqiang Wang > > Reviewed-by: Gavin Hu > > Signed-off-by: Lance Yang > > --- > > Compiler crashed while building DPDK: > > /home/travis/build/ovsrobot/ovs/dpdk-dir/drivers/net/ixgbe/ixgbe_pf.c: In > function > ‘ixgbe_pf_host_configure’: > /home/travis/build/ovsrobot/ovs/dpdk-dir/drivers/net/ixgbe/ixgbe_pf.c:297:1: > internal > compiler error: Segmentation fault > > https://travis-ci.org/ovsrobot/ovs/jobs/621434216#L1999 > > This is not good. > Need to check how frequently this happens. > > Best regards, Ilya Maximets. [Lance] I checked the report via the link you attached and re-triggered the build on my repo for several times. However, I could not reproduce it at this moment. We will research on this issue. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm
> -Original Message- > From: Ilya Maximets > Sent: Friday, November 29, 2019 3:06 AM > To: Lance Yang (Arm Technology China) ; Ilya Maximets > ; ovs-dev@openvswitch.org > Cc: Jieqiang Wang (Arm Technology China) ; Gavin Hu > (Arm > Technology China) ; Jingzhao Ni (Arm Technology China) > ; dwil...@us.ibm.com; nd ; Ruifeng Wang > (Arm > Technology China) ; Yanqin Wei (Arm Technology China) > > Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm > > On 27.11.2019 8:11, Lance Yang (Arm Technology China) wrote: > > > >> -Original Message- > >> From: Ilya Maximets > >> Sent: Friday, November 22, 2019 6:36 PM > >> To: Lance Yang (Arm Technology China) ; Ilya > >> Maximets ; ovs-dev@openvswitch.org > >> Cc: Jieqiang Wang (Arm Technology China) ; > >> Gavin Hu (Arm Technology China) ; Jingzhao Ni (Arm > >> Technology China) ; dwil...@us.ibm.com; nd > >> ; Ruifeng Wang (Arm Technology China) > >> ; Yanqin Wei (Arm Technology China) > >> > >> Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI > >> for arm > >> > >> On 22.11.2019 10:35, Lance Yang (Arm Technology China) wrote: > >>> Hi Ilya, > >>> > >>> Thanks for your reply. Please see the inline reply. > >>> > >>> Best regards, > >>> Lance Yang > >>> > >>>> -Original Message- > >>>> From: Ilya Maximets > >>>> Sent: Friday, November 22, 2019 3:47 AM > >>>> To: Lance Yang (Arm Technology China) ; ovs- > >>>> d...@openvswitch.org > >>>> Cc: Jieqiang Wang (Arm Technology China) ; > >>>> Gavin Hu (Arm Technology China) ; Jingzhao Ni > >>>> (Arm Technology China) ; dwil...@us.ibm.com; > >>>> nd ; Ruifeng Wang (Arm Technology China) > >>>> > >>>> Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI > >>>> for arm > >>>> > >>>> On 20.11.2019 9:15, Lance Yang wrote: > >>>>> Enable part of travis jobs with gcc compiler for arm64 > >>>>> architecture > >>>>> > >>>>> 1. Add arm jobs into the matrix in .travis.yml and define dpdk > >>>>> cache directory for arm64 architecture. > >>>>> 2. Temporarily disable sparse checker because of static code > >>>>> checking failure on arm64 > >>>> > >>>> Could you provide the sparse error messages? > >>>> Maybe we could fix them instead of disabling. > >>>> > >>>>> > >>>>> Successful travis build jobs report: > >>>>> https://travis-ci.org/yzyuestc/ovs/builds/614299933 > >>>> > >>>> There are some issues in Travis in above build. It seems that > >>>> Travis fails to upload the resulted cache directory due to missing > >>>> md5deep: > >>>> > >>>> "" > >>> [Lance] > >>> The issue occurred because sparse checker does not recognize some arm neon > intrinsics: > >>> > >>> 1. Some components in Open vSwitch source code directly includes the > >>> header file > >> . > >>> > >>> 2. When compiling OvS with DPDK, OvS includes some DPDK headers, > >>> which sometimes includes . You can see the details of > >>> the error in the report at: > >>> https://travis-ci.org/yzyuestc/ovs/jobs/615414391 > >>> after line 2693 > >>> > >>> For the first issue where OvS directly imported the arm_neon.h, I > >>> can fix it in my patch set > >> v2. However, for the second issue that DPDK project has imported the > >> arm neon intrinsics, it seems that I am unable to fix this issue until > >> DPDK solved it. > >> > >> Hi. > >> > >> Thanks for the information. > >> Could, you, please, check if the following patch fixes the issue: > >> https://patchwork.ozlabs.org/patch/1199398/ > >> ? > >> > >>> > >>>> store build cache > >>>> 0.02s5.41sInstalling md5deep > >>>> Reading package lists... > >>>> Building dependency tree... > >>>> Reading state information... > >>>> md5deep is already the newest version (4.4-2). > >>>> 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded. >
Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm
> -Original Message- > From: Ilya Maximets > Sent: Tuesday, November 26, 2019 8:48 PM > To: Ilya Maximets ; Lance Yang (Arm Technology China) > ; ovs-dev@openvswitch.org > Cc: Jieqiang Wang (Arm Technology China) ; Gavin Hu > (Arm > Technology China) ; Jingzhao Ni (Arm Technology China) > ; dwil...@us.ibm.com; nd ; Ruifeng Wang > (Arm > Technology China) ; Yanqin Wei (Arm Technology China) > ; Ben Pfaff > Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm > > On 26.11.2019 13:37, Ilya Maximets wrote: > > On 25.11.2019 7:28, Lance Yang (Arm Technology China) wrote: > >> > >> > >>> -Original Message- > >>> From: Ilya Maximets > >>> Sent: Friday, November 22, 2019 6:36 PM > >>> To: Lance Yang (Arm Technology China) ; Ilya > >>> Maximets ; ovs-dev@openvswitch.org > >>> Cc: Jieqiang Wang (Arm Technology China) ; > >>> Gavin Hu (Arm Technology China) ; Jingzhao Ni (Arm > >>> Technology China) ; dwil...@us.ibm.com; nd > >>> ; Ruifeng Wang (Arm Technology China) > >>> ; Yanqin Wei (Arm Technology China) > >>> > >>> Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI > >>> for arm > >>> > >>> On 22.11.2019 10:35, Lance Yang (Arm Technology China) wrote: > >>>> Hi Ilya, > >>>> > >>>> Thanks for your reply. Please see the inline reply. > >>>> > >>>> Best regards, > >>>> Lance Yang > >>>> > >>>>> -Original Message- > >>>>> From: Ilya Maximets > >>>>> Sent: Friday, November 22, 2019 3:47 AM > >>>>> To: Lance Yang (Arm Technology China) ; ovs- > >>>>> d...@openvswitch.org > >>>>> Cc: Jieqiang Wang (Arm Technology China) ; > >>>>> Gavin Hu (Arm Technology China) ; Jingzhao Ni > >>>>> (Arm Technology China) ; dwil...@us.ibm.com; > >>>>> nd ; Ruifeng Wang (Arm Technology China) > >>>>> > >>>>> Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI > >>>>> for arm > >>>>> > >>>>> On 20.11.2019 9:15, Lance Yang wrote: > >>>>>> Enable part of travis jobs with gcc compiler for arm64 > >>>>>> architecture > >>>>>> > >>>>>> 1. Add arm jobs into the matrix in .travis.yml and define dpdk > >>>>>> cache directory for arm64 architecture. > >>>>>> 2. Temporarily disable sparse checker because of static code > >>>>>> checking failure on arm64 > >>>>> > >>>>> Could you provide the sparse error messages? > >>>>> Maybe we could fix them instead of disabling. > >>>>> > >>>>>> > >>>>>> Successful travis build jobs report: > >>>>>> https://travis-ci.org/yzyuestc/ovs/builds/614299933 > >>>>> > >>>>> There are some issues in Travis in above build. It seems that > >>>>> Travis fails to upload the resulted cache directory due to missing > >>>>> md5deep: > >>>>> > >>>>> "" > >>>> [Lance] > >>>> The issue occurred because sparse checker does not recognize some arm > >>>> neon > intrinsics: > >>>> > >>>> 1. Some components in Open vSwitch source code directly includes > >>>> the header file > >>> . > >>>> > >>>> 2. When compiling OvS with DPDK, OvS includes some DPDK headers, > >>>> which sometimes includes . You can see the details of > >>>> the error in the report at: > >>>> https://travis-ci.org/yzyuestc/ovs/jobs/615414391 > >>>> after line 2693 > >>>> > >>>> For the first issue where OvS directly imported the arm_neon.h, I > >>>> can fix it in my patch set > >>> v2. However, for the second issue that DPDK project has imported the > >>> arm neon intrinsics, it seems that I am unable to fix this issue until > >>> DPDK solved it. > >>> > >>> Hi. > >>> > >>> Thanks for the information. > >>> Could, you, please, check if the following patch fixes the issue: > >>> https://patchwork.ozlabs.org/patch/1199398/ > >>&g
Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm
> -Original Message- > From: Ilya Maximets > Sent: Friday, November 22, 2019 6:36 PM > To: Lance Yang (Arm Technology China) ; Ilya Maximets > ; ovs-dev@openvswitch.org > Cc: Jieqiang Wang (Arm Technology China) ; Gavin Hu > (Arm > Technology China) ; Jingzhao Ni (Arm Technology China) > ; dwil...@us.ibm.com; nd ; Ruifeng Wang > (Arm > Technology China) ; Yanqin Wei (Arm Technology China) > > Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm > > On 22.11.2019 10:35, Lance Yang (Arm Technology China) wrote: > > Hi Ilya, > > > > Thanks for your reply. Please see the inline reply. > > > > Best regards, > > Lance Yang > > > >> -Original Message----- > >> From: Ilya Maximets > >> Sent: Friday, November 22, 2019 3:47 AM > >> To: Lance Yang (Arm Technology China) ; ovs- > >> d...@openvswitch.org > >> Cc: Jieqiang Wang (Arm Technology China) ; > >> Gavin Hu (Arm Technology China) ; Jingzhao Ni (Arm > >> Technology China) ; dwil...@us.ibm.com; nd > >> ; Ruifeng Wang (Arm Technology China) > >> > >> Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI > >> for arm > >> > >> On 20.11.2019 9:15, Lance Yang wrote: > >>> Enable part of travis jobs with gcc compiler for arm64 architecture > >>> > >>> 1. Add arm jobs into the matrix in .travis.yml and define dpdk cache > >>> directory for arm64 architecture. > >>> 2. Temporarily disable sparse checker because of static code > >>> checking failure on arm64 > >> > >> Could you provide the sparse error messages? > >> Maybe we could fix them instead of disabling. > >> > >>> > >>> Successful travis build jobs report: > >>> https://travis-ci.org/yzyuestc/ovs/builds/614299933 > >> > >> There are some issues in Travis in above build. It seems that Travis > >> fails to upload the resulted cache directory due to missing md5deep: > >> > >> "" > > [Lance] > > The issue occurred because sparse checker does not recognize some arm neon > > intrinsics: > > > > 1. Some components in Open vSwitch source code directly includes the header > > file > . > > > > 2. When compiling OvS with DPDK, OvS includes some DPDK headers, which > > sometimes includes . You can see the details of the error > > in the report at: https://travis-ci.org/yzyuestc/ovs/jobs/615414391 > > after line 2693 > > > > For the first issue where OvS directly imported the arm_neon.h, I can fix > > it in my patch set > v2. However, for the second issue that DPDK project has imported the arm neon > intrinsics, it > seems that I am unable to fix this issue until DPDK solved it. > > Hi. > > Thanks for the information. > Could, you, please, check if the following patch fixes the issue: > https://patchwork.ozlabs.org/patch/1199398/ > ? > > > > >> store build cache > >> 0.02s5.41sInstalling md5deep > >> Reading package lists... > >> Building dependency tree... > >> Reading state information... > >> md5deep is already the newest version (4.4-2). > >> 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded. > >> /home/travis/.casher/bin/casher: line 230: md5deep: command not found > >> nothing changed "" > >> > > [Lance] > > Thanks for pointing out the issue. The upload cache on arm is not > > successful, that means arm jobs will always clone and build DPDK. I > > just posted this issue to Travis CI community. You can see: > > https://travis-ci.community/t/no-cache-support-on-arm64/5416/21 > > Thanks! Let's wait for their reply. > > Best regards, Ilya Maximets. [Lance] Hi Ilya, It seems that travis CI has fixed the md5deep: command not found issue. You can refer the link: https://travis-ci.community/t/no-cache-support-on-arm64/5416/23?u=yzyuestc. And if you check https://travis-ci.community/t/no-cache-support-on-arm64/5416/26?u=yzyuestc, you will find Travis has deployed it to production. I triggered a build and found it works, the report on line 5093: https://travis-ci.org/yzyuestc/ovs/jobs/616991450#L5093 It shows the correct directory has been uploaded successfully. Best regards, Lance IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm
> -Original Message- > From: Ilya Maximets > Sent: Friday, November 22, 2019 6:36 PM > To: Lance Yang (Arm Technology China) ; Ilya Maximets > ; ovs-dev@openvswitch.org > Cc: Jieqiang Wang (Arm Technology China) ; Gavin Hu > (Arm > Technology China) ; Jingzhao Ni (Arm Technology China) > ; dwil...@us.ibm.com; nd ; Ruifeng Wang > (Arm > Technology China) ; Yanqin Wei (Arm Technology China) > > Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm > > On 22.11.2019 10:35, Lance Yang (Arm Technology China) wrote: > > Hi Ilya, > > > > Thanks for your reply. Please see the inline reply. > > > > Best regards, > > Lance Yang > > > >> -Original Message----- > >> From: Ilya Maximets > >> Sent: Friday, November 22, 2019 3:47 AM > >> To: Lance Yang (Arm Technology China) ; ovs- > >> d...@openvswitch.org > >> Cc: Jieqiang Wang (Arm Technology China) ; > >> Gavin Hu (Arm Technology China) ; Jingzhao Ni (Arm > >> Technology China) ; dwil...@us.ibm.com; nd > >> ; Ruifeng Wang (Arm Technology China) > >> > >> Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI > >> for arm > >> > >> On 20.11.2019 9:15, Lance Yang wrote: > >>> Enable part of travis jobs with gcc compiler for arm64 architecture > >>> > >>> 1. Add arm jobs into the matrix in .travis.yml and define dpdk cache > >>> directory for arm64 architecture. > >>> 2. Temporarily disable sparse checker because of static code > >>> checking failure on arm64 > >> > >> Could you provide the sparse error messages? > >> Maybe we could fix them instead of disabling. > >> > >>> > >>> Successful travis build jobs report: > >>> https://travis-ci.org/yzyuestc/ovs/builds/614299933 > >> > >> There are some issues in Travis in above build. It seems that Travis > >> fails to upload the resulted cache directory due to missing md5deep: > >> > >> "" > > [Lance] > > The issue occurred because sparse checker does not recognize some arm neon > > intrinsics: > > > > 1. Some components in Open vSwitch source code directly includes the header > > file > . > > > > 2. When compiling OvS with DPDK, OvS includes some DPDK headers, which > > sometimes includes . You can see the details of the error > > in the report at: https://travis-ci.org/yzyuestc/ovs/jobs/615414391 > > after line 2693 > > > > For the first issue where OvS directly imported the arm_neon.h, I can fix > > it in my patch set > v2. However, for the second issue that DPDK project has imported the arm neon > intrinsics, it > seems that I am unable to fix this issue until DPDK solved it. > > Hi. > > Thanks for the information. > Could, you, please, check if the following patch fixes the issue: > https://patchwork.ozlabs.org/patch/1199398/ > ? [Lance] Thanks for your reply. I downloaded and applied the patch from patchwork. However, it seems that the patch does not work as expected. I attached the original travis report link: https://travis-ci.org/yzyuestc/ovs/jobs/616442657#L2692. You can check the error after line 2692. Thanks for your time. > > > > >> store build cache > >> 0.02s5.41sInstalling md5deep > >> Reading package lists... > >> Building dependency tree... > >> Reading state information... > >> md5deep is already the newest version (4.4-2). > >> 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded. > >> /home/travis/.casher/bin/casher: line 230: md5deep: command not found > >> nothing changed "" > >> > > [Lance] > > Thanks for pointing out the issue. The upload cache on arm is not > > successful, that means arm jobs will always clone and build DPDK. I > > just posted this issue to Travis CI community. You can see: > > https://travis-ci.community/t/no-cache-support-on-arm64/5416/21 > > Thanks! Let's wait for their reply. > > Best regards, Ilya Maximets. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH v1 1/4] dpif-netdev: Fix the pmd_perf_stats
Hi Ilya,
Thanks for your comments. Please take time to see the inline comments.
Best regards,
Lance
> -Original Message-
> From: Ilya Maximets
> Sent: Friday, November 22, 2019 3:23 AM
> To: Lance Yang (Arm Technology China) ; ovs-
> d...@openvswitch.org
> Cc: Jieqiang Wang (Arm Technology China) ; Gavin Hu
> (Arm
> Technology China) ; Jingzhao Ni (Arm Technology China)
> ; nd ; Ruifeng Wang (Arm Technology China)
>
> Subject: Re: [ovs-dev] [PATCH v1 1/4] dpif-netdev: Fix the pmd_perf_stats
>
> On 20.11.2019 9:13, Lance Yang wrote:
> > When compiling Open vSwitch for aarch64, the compiler will warn about
> > an uninitialized variable in lib/dpif-netdev-perf.c. It is necessary
> > to initialize it to avoid build failure.
>
> Hi. Thanks for making OVS build on aarch64.
>
> Could you provide the error message?
[Lance]
For the error message you would like to see, I copied it below:
--- Begin of the error message ---
In file included from lib/dpif-netdev-perf.c:21:
lib/dpif-netdev-perf.c: In function 'pmd_perf_estimate_tsc_frequency':
lib/dpif-netdev-perf.h:198:16: error: 's.last_tsc' may be used uninitialized in
this function [-Werror=maybe-uninitialized]
return s->last_tsc;
~^~
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I ./include -I ./include -I ./lib
-I ./lib -Wstrict-prototypes -Wall -Wextra -Wno-sign-compare -Wpointer-arith
-Wformat -Wformat-security -Wswitch-enum -Wunused-parameter -Wbad-function-cast
-Wcast-align -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes
-Wmissing-field-initializers -fno-strict-aliasing -Wswitch-bool
-Wlogical-not-parentheses -Wsizeof-array-argument -Wbool-compare
-Wshift-negative-value -Wduplicated-cond -Wshadow -Wmultistatement-macros
-Wcast-align=strict -Werror -Werror -g -O2 -MT lib/heap.lo -MD -MP -MF
lib/.deps/heap.Tpo -c lib/heap.c -o lib/heap.o
cc1: all warnings being treated as errors
--- end of the message---
191 static inline uint64_t
192 rdtsc_syscall(struct pmd_perf_stats *s)
193 {
194 struct timespec val;
195 uint64_t v;
196
197 if (clock_gettime(CLOCK_MONOTONIC_RAW, ) != 0) {
198return s->last_tsc;
199 }
200
201 v = val.tv_sec * UINT64_C(10) + val.tv_nsec;
202 return s->last_tsc = v;
203 }
204 #endif
When the clock_gettime function failed, the code "return s->last_tsc" will be
reached.
> In fact this variable is never used (only assigned), so this should be a
> false-positive. So, I'd
> like to look at the error message.
>
> Also, it might be better to rename the patch to something more specific. e.g.
> 'dpif-netdev-perf: Avoid false-positive on uninitialized perf stats.'
I typed an "Enter key" in the patch. The original title should be:
Subject: [ovs-dev] [PATCH v1 1/4] dpif-netdev: Fix the pmd_perf_stats
uninitalized issue
If this title looks fine, I will modify the title as above in the patch set v2.
> >
> > Reviewed-by: Yanqin Wei
> > Signed-off-by: Lance Yang
> > ---
> > lib/dpif-netdev-perf.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/lib/dpif-netdev-perf.c b/lib/dpif-netdev-perf.c index
> > baf90b0..f85bb0c 100644
> > --- a/lib/dpif-netdev-perf.c
> > +++ b/lib/dpif-netdev-perf.c
> > @@ -63,6 +63,7 @@ pmd_perf_estimate_tsc_frequency(void)
> > struct pmd_perf_stats s;
> > uint64_t start, stop;
> >
> > +memset(, 0, sizeof(s));
>
> Please, don't parenthesize the argument of a 'sizeof'.
>
> Also, it might be better to initialize the variable close to the first usage.
> It doesn't look
> good here.
>
[Lance]
I will remove the parenthesize for the sizeof operator and move the struct
initialization closer to where it is used.
> > /* DPDK is not available or returned unreliable value.
> > * Trying to estimate. */
> > affinity = ovs_numa_thread_getaffinity_dump();
> >
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH v1 3/4] travis: split cache and set target for
Hi Ilya, Thanks for your comments. > -Original Message- > From: Ilya Maximets > Sent: Friday, November 22, 2019 3:39 AM > To: Lance Yang (Arm Technology China) ; ovs- > d...@openvswitch.org > Cc: Jieqiang Wang (Arm Technology China) ; Gavin Hu > (Arm > Technology China) ; Jingzhao Ni (Arm Technology China) > ; dwil...@us.ibm.com; nd ; Ruifeng Wang > (Arm > Technology China) > Subject: Re: [ovs-dev] [PATCH v1 3/4] travis: split cache and set target for > > On 20.11.2019 9:15, Lance Yang wrote: > > To compile OvS with DPDK in some Travis jobs, it is necessary to set > > the build target and split the dpdk cache directory according to > > different CPU architectures. > > > > Reviewed-by: Yanqin Wei > > Reviewed-by: Malvika Gupta > > Signed-off-by: Lance Yang > > --- > > .travis/linux-build.sh | 32 +--- > > 1 file changed, 21 insertions(+), 11 deletions(-) > > > According to this thread: > https://travis-ci.community/t/no-cache-support-on-arm64/5416/20 > > The arch name should be included now in the cache key, so this should not be > an issue. > Could you, please, re-check? > [Lance] I rechecked Travis CI. I found the cache conflict issue was solved. But the upload cache function on arm is still not successful. I will remove cache split in v2. > Best regards, Ilya Maximets. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm
Hi Ilya, Thanks for your reply. Please see the inline reply. Best regards, Lance Yang > -Original Message- > From: Ilya Maximets > Sent: Friday, November 22, 2019 3:47 AM > To: Lance Yang (Arm Technology China) ; ovs- > d...@openvswitch.org > Cc: Jieqiang Wang (Arm Technology China) ; Gavin Hu > (Arm > Technology China) ; Jingzhao Ni (Arm Technology China) > ; dwil...@us.ibm.com; nd ; Ruifeng Wang > (Arm > Technology China) > Subject: Re: [ovs-dev] [PATCH v1 4/4] travis: Enable OVS Travis CI for arm > > On 20.11.2019 9:15, Lance Yang wrote: > > Enable part of travis jobs with gcc compiler for arm64 architecture > > > > 1. Add arm jobs into the matrix in .travis.yml and define dpdk cache > > directory for arm64 architecture. > > 2. Temporarily disable sparse checker because of static code checking > > failure on arm64 > > Could you provide the sparse error messages? > Maybe we could fix them instead of disabling. > > > > > Successful travis build jobs report: > > https://travis-ci.org/yzyuestc/ovs/builds/614299933 > > There are some issues in Travis in above build. It seems that Travis fails > to upload the > resulted cache directory due to missing md5deep: > > "" [Lance] The issue occurred because sparse checker does not recognize some arm neon intrinsics: 1. Some components in Open vSwitch source code directly includes the header file . 2. When compiling OvS with DPDK, OvS includes some DPDK headers, which sometimes includes . You can see the details of the error in the report at: https://travis-ci.org/yzyuestc/ovs/jobs/615414391 after line 2693 For the first issue where OvS directly imported the arm_neon.h, I can fix it in my patch set v2. However, for the second issue that DPDK project has imported the arm neon intrinsics, it seems that I am unable to fix this issue until DPDK solved it. > store build cache > 0.02s5.41sInstalling md5deep > Reading package lists... > Building dependency tree... > Reading state information... > md5deep is already the newest version (4.4-2). > 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded. > /home/travis/.casher/bin/casher: line 230: md5deep: command not found nothing > changed "" > [Lance] Thanks for pointing out the issue. The upload cache on arm is not successful, that means arm jobs will always clone and build DPDK. I just posted this issue to Travis CI community. You can see: https://travis-ci.community/t/no-cache-support-on-arm64/5416/21 > Best regards, Ilya Maximets. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [bug-report] Check Python IDL reconnects to leader unit case failed on arm64
Hi Ben, Thanks for your reply. I checked the original email I sent. I did attach the logs in my previous email. However, as you said, they might be stripped automatically. At this time, I compress everything into a zip file. I am not sure whether it would be stripped again. So I also attach a link where you can find the related logs: https://1drv.ms/u/s!Atj0ulDEFFyaj1ds2QyEmPMkRM9s?e=Ifr7l9 . For convenience, I also copied the original email content as below in case that you did not receive the complete message: I encountered an issue when I was running testsuite on Arm. The system I tested on was an arm server running Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-65-generic aarch64). After I downloaded the up-to-date source code on master branch and built ovs, I run the testsuite with TESTSUITEFLAGS="2105" (Unit case name: Check Python IDL reconnects to leader) I run the unit case for many times, most of the time I got the following failure: make check TESTSUITEFLAGS="2105" RECHECK=yes make check-recursive make[1]: Entering directory '/home/lance/ovs' Making check in datapath make[2]: Entering directory '/home/lance/ovs/datapath' make[3]: Entering directory '/home/lance/ovs/datapath' make[3]: Leaving directory '/home/lance/ovs/datapath' make[2]: Leaving directory '/home/lance/ovs/datapath' make[2]: Entering directory '/home/lance/ovs' make[3]: Entering directory '/home/lance/ovs/datapath' make[3]: 'distfiles' is up to date. make[3]: Leaving directory '/home/lance/ovs/datapath' make utilities/ovs-appctl-bashcomp.bash utilities/ovs-vsctl-bashcomp.bash tests/atlocal make[3]: Entering directory '/home/lance/ovs' make[3]: Nothing to be done for 'utilities/ovs-appctl-bashcomp.bash'. make[3]: Nothing to be done for 'utilities/ovs-vsctl-bashcomp.bash'. make[3]: 'tests/atlocal' is up to date. make[3]: Leaving directory '/home/lance/ovs' make check-local make[3]: Entering directory '/home/lance/ovs' set /bin/bash './tests/testsuite' -C tests AUTOTEST_PATH=utilities:vswitchd:ovsdb:vtep:tests::; \ "$@" -j2 2104-2105 || (test X'' = Xyes && "$@" --recheck) ## --- ## ## openvswitch 2.12.90 test suite. ## ## --- ## 2105: Check Python IDL reconnects to leader - Python3 (leader only) FAILED (ovsdb-idl.at:1816) ## - ## ## Test results. ## ## - ## ERROR: All 1 test was run, 1 failed unexpectedly. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: Subject: [openvswitch 2.12.90] testsuite: 2105 failed You may investigate any problem if you feel able to do so, in which case the test suite provides a good starting point. Its output may be found below `tests/testsuite.dir'. ## --- ## 2105: Check Python IDL reconnects to leader - Python3 (leader only) FAILED (ovsdb-idl.at:1816) ## - ## ## Test results. ## ## - ## ERROR: 1 test was run, 1 failed unexpectedly. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: Subject: [openvswitch 2.12.90] testsuite: 2105 failed You may investigate any problem if you feel able to do so, in which case the test suite provides a good starting point. Its output may be found below `tests/testsuite.dir'. Makefile:6151: recipe for target 'check-local' failed make[3]: *** [check-local] Error 1 make[3]: Leaving directory '/home/lance/ovs' Makefile:5275: recipe for target 'check-am' failed make[2]: *** [check-am] Error 2 make[2]: Leaving directory '/home/lance/ovs' Makefile:4984: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory '/home/lance/ovs' Makefile:5278: recipe for target 'check' failed make: *** [check] Error 2 I attached the tests/testsuite.dir/testsuite.log to this email. I also attached the logs for ovsdb. Any hints on what is wrong here? Thank you so much. Best regards, Lance Yang > -Original Message- > From: Ben Pfaff > Sent: Friday, November 22, 2019 9:10 AM > To: Lance Yang (Arm Technology China) > Cc: b...@openvswitch.org; ovs-dev@openvswitch.org; ted.elhour...@nutanix.com > Subject: Re: [ovs-dev] [bug-report] Check Python IDL reconnects to leader > unit case failed > on arm64 > > On Thu, Nov 21, 2019 at 07:54:09AM +, Lance Yang (Arm Technology China) > wrote: > > Hi, > > I encountered an issue when I was running testsuite on Arm. > > The system I tested on was an arm server running Ubuntu 18.04.3 LTS > > (GNU/Linux > 4.15.0-65-generic aarch64). > > After I downloaded the up-to-date source code on master branch and built > > ovs, I run the > testsuite with TESTSUITEFLA
[ovs-dev] [bug-report] bfd decay unit case failure
Hi, I encountered a unit test failure when I ran the Open vSwitch testsuite on Travis CI aarch64 lxd container. The environment can be found at line 7 : build system information section in the report on https://travis-ci.org/yzyuestc/ovs/jobs/614941322 . The unit test case name is "bfd decay" , you can find the unit test failure details in the report after line 6520. The failure is not 100% reproducible on Travis CI. Could anyone give some hint on what is wrong for this unit test case? Best regards, Lance IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
[ovs-dev] [bug-report] Check Python IDL reconnects to leader unit case failed on arm64
Hi, I encountered an issue when I was running testsuite on Arm. The system I tested on was an arm server running Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-65-generic aarch64). After I downloaded the up-to-date source code on master branch and built ovs, I run the testsuite with TESTSUITEFLAGS="2105" (Unit case name: Check Python IDL reconnects to leader) I run the unit case for many times, most of the time I got the following failure: make check TESTSUITEFLAGS="2105" RECHECK=yes make check-recursive make[1]: Entering directory '/home/lance/ovs' Making check in datapath make[2]: Entering directory '/home/lance/ovs/datapath' make[3]: Entering directory '/home/lance/ovs/datapath' make[3]: Leaving directory '/home/lance/ovs/datapath' make[2]: Leaving directory '/home/lance/ovs/datapath' make[2]: Entering directory '/home/lance/ovs' make[3]: Entering directory '/home/lance/ovs/datapath' make[3]: 'distfiles' is up to date. make[3]: Leaving directory '/home/lance/ovs/datapath' make utilities/ovs-appctl-bashcomp.bash utilities/ovs-vsctl-bashcomp.bash tests/atlocal make[3]: Entering directory '/home/lance/ovs' make[3]: Nothing to be done for 'utilities/ovs-appctl-bashcomp.bash'. make[3]: Nothing to be done for 'utilities/ovs-vsctl-bashcomp.bash'. make[3]: 'tests/atlocal' is up to date. make[3]: Leaving directory '/home/lance/ovs' make check-local make[3]: Entering directory '/home/lance/ovs' set /bin/bash './tests/testsuite' -C tests AUTOTEST_PATH=utilities:vswitchd:ovsdb:vtep:tests::; \ "$@" -j2 2104-2105 || (test X'' = Xyes && "$@" --recheck) ## --- ## ## openvswitch 2.12.90 test suite. ## ## --- ## 2105: Check Python IDL reconnects to leader - Python3 (leader only) FAILED (ovsdb-idl.at:1816) ## - ## ## Test results. ## ## - ## ERROR: All 1 test was run, 1 failed unexpectedly. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: Subject: [openvswitch 2.12.90] testsuite: 2105 failed You may investigate any problem if you feel able to do so, in which case the test suite provides a good starting point. Its output may be found below `tests/testsuite.dir'. ## --- ## 2105: Check Python IDL reconnects to leader - Python3 (leader only) FAILED (ovsdb-idl.at:1816) ## - ## ## Test results. ## ## - ## ERROR: 1 test was run, 1 failed unexpectedly. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: Subject: [openvswitch 2.12.90] testsuite: 2105 failed You may investigate any problem if you feel able to do so, in which case the test suite provides a good starting point. Its output may be found below `tests/testsuite.dir'. Makefile:6151: recipe for target 'check-local' failed make[3]: *** [check-local] Error 1 make[3]: Leaving directory '/home/lance/ovs' Makefile:5275: recipe for target 'check-am' failed make[2]: *** [check-am] Error 2 make[2]: Leaving directory '/home/lance/ovs' Makefile:4984: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory '/home/lance/ovs' Makefile:5278: recipe for target 'check' failed make: *** [check] Error 2 I attached the tests/testsuite.dir/testsuite.log to this email. I also attached the logs for ovsdb. Any hints on what is wrong here? Thank you so much. Best regards, Lance Yang IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Re: [ovs-dev] [PATCH v3] travis: support ppc64le builds
Hi, For pip missing issue, we have a workaround. In .travis/linux-prepare.sh. You can install pip or something else with package management commands. For arm64 on travis, we check the environment variables in the container and found a variable called "TRAVIS_ARCH". Thus we can use this variable to install specific software for a specific CPU architecture. You can find a successful build here: https://travis-ci.org/yzyuestc/ovs/jobs/610716477 -Original Message- From: ovs-dev-boun...@openvswitch.org On Behalf Of dwilder Sent: Wednesday, November 13, 2019 8:29 AM To: Ilya Maximets Cc: ovs-dev@openvswitch.org; wil...@us.ibm.com Subject: Re: [ovs-dev] [PATCH v3] travis: support ppc64le builds On 2019-11-12 11:30, Ilya Maximets wrote: > On 12.11.2019 18:57, dwilder wrote: >> On 2019-11-08 14:52, Ilya Maximets wrote: >>> On 06.11.2019 20:20, David Wilder wrote: Add support for travis-ci ppc64le builds. - Updated matrix in .travis.yml to include an arch: ppc64le build. - Move package install needed for 32bit builds to .travis/linux-prepare.sh. To keep the total build time at an acceptable level only a single build job is included in the matrix for ppc64le. A build report example can be found here [1] [0] https://urldefense.proofpoint.com/v2/url?u=http-3A__travis-2Dci.org _=DwICaQ=jf_iaSHvJObTbx-siA1ZOg=7ndxyKjH9UrBD68Us2WP1wI4BwEBQ beAyz8i_vwCCaI=_UtshYcJsj4Pt3b9hfgEiyaEIT3j9gPEIgmBatCEqCo=r0fB Os-21CKcV4kyZGnzh3fcjrpR8caYSl8K2i1St54= [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.or g_djlwilder_ovs_builds_607851729=DwICaQ=jf_iaSHvJObTbx-siA1ZOg& r=7ndxyKjH9UrBD68Us2WP1wI4BwEBQbeAyz8i_vwCCaI=_UtshYcJsj4Pt3b9hfg EiyaEIT3j9gPEIgmBatCEqCo=7t2rzVasH7Xq_R7jWkWZO9rkgm4KHMH-WavBzCRb F74= Signed-off-by: David Wilder --- Addressed review comments: - Cleaned up linux-prepare.sh (v2) - Switch from os: linux-ppc64le to arch: ppc64le (v3) >>> >>> What a wonderful world of undocumented features. :) >>> >>> Anyway, I just tried this patch and it fails for me because of >>> missing pip: >>> >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org >>> _igsilya_ovs_jobs_609402867=DwICaQ=jf_iaSHvJObTbx-siA1ZOg=7ndx >>> yKjH9UrBD68Us2WP1wI4BwEBQbeAyz8i_vwCCaI=_UtshYcJsj4Pt3b9hfgEiyaEIT >>> 3j9gPEIgmBatCEqCo=PF1oO_KkZFd_RRKToj6UBN2t2YhvTVE5XnVD1GF9u60= >>> >>> pip install --disable-pip-version-check --user six flake8 hacking >>> ./.travis/linux-prepare.sh: line 15: pip: command not found >>> >>> Restarting the job doesn't help. >>> >>> I'm wondering what is the base image and who controls preinstalled >>> software? >>> Maybe it makes sense to hold on until travis will start supporting >>> ppc64le officially? >>> >>> Best regards, Ilya Maximets. >> >> Unfortunately it not just ppc the arm64 image has the same issue :) I >> added a arm64 build on this attempt. >> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_ >> djlwilder_ovs_builds_610517731=DwIDaQ=jf_iaSHvJObTbx-siA1ZOg=7n >> dxyKjH9UrBD68Us2WP1wI4BwEBQbeAyz8i_vwCCaI=rVTSRTh9jExG_mX8boqA-OQcZ >> kWmbO2g7TjgtUe6jws=sCvTr8MwXrqa7AEOs60tuqnquBqbRKlp_7-WacGzJWc= >> >> I will attempt to adjust the package list. > > I think, you could just report this to TravisCI support and see what > they will answer. It'll be much better if they will just update their > images. > > And the good news that ppc64le is officially supported now: > https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.travis-2Dci. > com_2019-2D11-2D12-2Dmulti-2Dcpu-2Darchitecture-2Dibm-2Dpower-2Dibm-2D > z=DwIDaQ=jf_iaSHvJObTbx-siA1ZOg=7ndxyKjH9UrBD68Us2WP1wI4BwEBQbeA > yz8i_vwCCaI=rVTSRTh9jExG_mX8boqA-OQcZkWmbO2g7TjgtUe6jws=CRYw9o6At3 > rFT_gd_5r1Uw07mv_SEPvQ6LgBLfMyqgg= That is great news! I reported the issue to travis: https://travis-ci.community/t/pip-is-not-installed-in-ppc64le-and-arm64-images/5902?u=djlwilder I added a workaround if we need it. This is my latest travis run. https://www.travis-ci.org/djlwilder/ovs/builds/611123734 ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
