up
when trying to squeeze maximum performance from a given system.
D.
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
Konrad Gutkowski
Sent: Saturday, February 24, 2018 9:07 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] clib_time_now
Hardware as
mance from a given system.
D.
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
Konrad Gutkowski
Sent: Saturday, February 24, 2018 9:07 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] clib_time_now
Hardware as requested:
Platform: Intel S2600W
Behalf Of Konrad
Gutkowski
Sent: Saturday, February 24, 2018 9:07 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] clib_time_now
Hardware as requested:
Platform: Intel S2600WF
Affected cpu 6130, 6130T
Various nic's all connected to socket 2
Same platform with 5122 and 6134 seems to wor
niu 24.02.2018 o 14:19 Dave Barach pisze:
If you don't describe the "specific hardware configuration," we can't
help you.
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
Konrad Gutkowski
Sent: Friday, February 23, 2018 9:10 PM
If you don't describe the "specific hardware configuration," we can't help you.
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Konrad
Gutkowski
Sent: Friday, February 23, 2018 9:10 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-de
Hi,
If I'm reading this correctly clib_time_verify_frequency takes into
considetation only recent tick's, while the result is applied to the total
number of tick's since program start.
From what I saw, in normal circumstances with cpu speed scaling it will
very rarely lead to main thread
