[RFC] Telemetry enhancements and Windows support

Dmitry Kozlyuk dmitry.kozliuk at gmail.com
Thu Apr 7 00:03:21 CEST 2022


2022-04-06 14:57 (UTC-0700), Stephen Hemminger:
> On Thu, 7 Apr 2022 00:50:29 +0300
> Dmitry Kozlyuk <dmitry.kozliuk at gmail.com> 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.    
> > 
> > Scope is a strong valid argument.
> > What do you think if telemetry would create threads using Win32 API
> > just like on Unices it creates threads using pthread
> > (external component that is always present)?  
> 
> Why isn't telemetry using existing rte_ctrl_thread API?

It would depend on EAL at link time then.
But EAL already depends on telemetry and there would be a loop.


More information about the dev mailing list