2022-04-06 14:57 (UTC-0700), Stephen Hemminger:
> On Thu, 7 Apr 2022 00:50:29 +0300
> Dmitry Kozlyuk wrote:
>
> > 2022-04-04 11:03 (UTC+0100), Bruce Richardson:
> > [...]
> > > Having EAL be the only one to create threads seems reasonable. However,
> > > I'm
> > > a little uncertain about the
On Thu, 7 Apr 2022 00:50:29 +0300
Dmitry Kozlyuk wrote:
> 2022-04-04 11:03 (UTC+0100), Bruce Richardson:
> [...]
> > Having EAL be the only one to create threads seems reasonable. However, I'm
> > a little uncertain about the scope of change and tying telemetry and EAL
> > together a lot more.
2022-04-04 11:03 (UTC+0100), Bruce Richardson:
[...]
> Having EAL be the only one to create threads seems reasonable. However, I'm
> a little uncertain about the scope of change and tying telemetry and EAL
> together a lot more.
Scope is a strong valid argument.
What do you think if telemetry woul
On Sat, Apr 02, 2022 at 01:59:01AM +0300, Dmitry Kozlyuk wrote:
> Vipin from AMD expressed demand for telemetry support on Windows
> in order to collect port statistics.
> Implementing a PoC, he stumbled several issues.
> Together we have designed a solution that eliminates these issues.
> It affec
2022-04-02 01:59 (UTC+0300), Dmitry Kozlyuk:
> Telemetry today (talking only about v2):
>
> * Telemetry library starts a thread to listen for connections.
> It is affinitized to the main lcore.
Should be: "to the control thread CPU set".
> A thread is spawned to serve each client connection.
Vipin from AMD expressed demand for telemetry support on Windows
in order to collect port statistics.
Implementing a PoC, he stumbled several issues.
Together we have designed a solution that eliminates these issues.
It affects telemetry operation for all platforms, at least code-wise,
We would lik
6 matches
Mail list logo
