search

pinggit / dpdk-contrail-book

contrail dpdk day one book
9 stars 3 forks source link

thread pinning in log message #7

Closed pinggit closed 4 years ago

pinggit commented 4 years ago

here says:

VROUTER: --lcores "(0-2)@(0-47),(8-9)@(0-47),*10@2,11@4,12@6,13@8,14@26,15@28,16@30,17@32*"
EAL: Detected 48 lcore(s)
*VROUTER: Using 8 forwarding lcore(s)*
VROUTER: Using 0 IO lcore(s)
VROUTER: Using 5 service lcores
First part of the message - (0-2)@(0-N),(8-9)@(0-N) - is always the same, as this internal CPU logical numbering is statically defined in vrouter source code.

...

so this looks service thread info (which is NOT pinned according to this specific log snippet). thread 0, 1, 2, 8, 9. we probably should mention it clearly.

ldurandadomia commented 4 years ago

Hello Ping,

"First part of the message - (0-2)@(0-N),(8-9)@(0-N) - is always the same," It was true up 20.03 release. Since 20.03, we have a new parameter supported on vRouter which is now allowing to pin service threads on a given CPU list: _--service_coremask : (20.03 and later version) CPUs to be used for vrouter service threads (CPU list or hexadecimal bitmask)

So, it should be different now. first part of the message should be: (0-2)@("service core list"),(8-9)@("service core list")

To be checked on 20.03 or 20.06 release.

Laurent

pinggit commented 4 years ago

thanks laurent, I meant we should mention it is service threads, which is not mentioned in the explanation.