Each released nsx-ovs windows version is signed build and it could get
related pdb files for ovs userspace binary file and ovsext driver.
Regards
Wilson
On Fri, Jul 12, 2024 at 4:09 PM Wenying Dong <wenying.d...@broadcom.com>
wrote:
> @Wilson Peng <wilson.p...@broadcom.com> ,
>
> About the below question, do we have the pdbs if the nsx-ovs version is
> known?
>
> > the problem is that I have no debug symbols and the libraries have no
> version information compiled into them so I cannot even ask for pdbs for a
> specific version.
>
> Should I get pdbs from VMWare or do they supply symbols for these things
> somewhere e.g. a symbol server?
>
>
> Best,
>
> Wenying
>
> On Fri, Jul 12, 2024 at 3:51 PM Alin Serdean <alinserd...@gmail.com>
> wrote:
>
>>
>> I'm adding @Wenying Dong <wenying.d...@broadcom.com> , from the Antrea
>> team to the thread who might know the answer to your questions..
>>
>> It might be useful to some information about ovs usage i.e. "ovs-appctl
>> {dpctl/show,dpctl/dump-flows,coverage/show", also the vswitchd/ovsdb logs.
>>
>> --
>> Alin
>>
>> On Fri, Jul 12, 2024 at 7:45 AM Kraus, Alois <
>> alois.kr...@siemens-healthineers.com> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> the problem is that I have no debug symbols and the libraries have no
>>> version information compiled into them so I cannot even ask for pdbs for a
>>> specific version.
>>>
>>> Should I get pdbs from VMWare or do they supply symbols for these things
>>> somewhere e.g. a symbol server?
>>>
>>>
>>>
>>> Yours,
>>>
>>> Alois Kraus, Alois (SHS DI SY R&D AS SE)
>>>
>>>
>>>
>>>
>>>
>>> *From:* Alin Serdean <alinserd...@gmail.com>
>>> *Sent:* Thursday, July 11, 2024 5:00 PM
>>> *To:* Eelco Chaudron <echau...@redhat.com>
>>> *Cc:* Kraus, Alois <alois.kr...@siemens-healthineers.com>;
>>> b...@openvswitch.org
>>> *Subject:* Re: [ovs-discuss] High CPU of ovs-vswitchd.exe
>>>
>>>
>>>
>>> You don't often get email from alinserd...@gmail.com. Learn why this is
>>> important <https://aka.ms/LearnAboutSenderIdentification>
>>>
>>> FWIW the windows datapath does not have megaflows implemented.
>>>
>>> The expectation is to have a huge number of DP flows on a busy system.
>>>
>>>
>>>
>>> --
>>>
>>> Alin.
>>>
>>>
>>>
>>> On Thu, Jul 11, 2024 at 2:12 PM Eelco Chaudron via discuss <
>>> ovs-discuss@openvswitch.org> wrote:
>>>
>>>
>>>
>>> On 11 Jul 2024, at 11:42, Kraus, Alois via discuss wrote:
>>>
>>> > Hi,
>>> >
>>> > is this the right place to report this? I have observed pretty high
>>> CPU of ovs-vswitchd.exe even when the (Tanzu) VM is idle.
>>> > It seems to poll every 500ms on 4 threads for 70ms
>>> >
>>> > [cid:image001.png@01DAD387.07AFD320]
>>> >
>>> >
>>> > [cid:image002.png@01DAD387.07AFD320]
>>> >
>>> >
>>> > This seems to be consumed by PThreadVC2 library which most likely does
>>> an excessive amount of CPU spinning just to find that no one did wake up.
>>> CPU spinning is meant for Spinlocks in the range of sub ms or a few ms at
>>> most but not for such long times.
>>> >
>>> > [cid:image003.png@01DAD387.616F9800]
>>> >
>>> >
>>> > Where can I report this one? We would like to do something more useful
>>> with our cores than CPU spinning.
>>>
>>> 500ms sounds like the revalidator threads kicking in. If there are no DP
>>> rules, it should not take much CPU (at least on the Linux builds). If you
>>> are sure it’s all in the PThreadVC2 library, digging into that part might
>>> be the best next step. Sorry, I have no experience with the windows builds.
>>>
>>> //Eelco
>>>
>>> > Yours,
>>> > Alois
>>>
>>> > _______________________________________________
>>> > discuss mailing list
>>> > disc...@openvswitch.org
>>> > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>>
>>> _______________________________________________
>>> discuss mailing list
>>> disc...@openvswitch.org
>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>>
>>>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
