undefined | Better HN

0 pointssaagarjha3y ago0 comments

I don’t see how? Once your quantum is up the thread gets put back into the scheduling pool and you have to do this all over again…

0 comments

boardwaalk3y ago

Couldn’t there be some flag on the thread that marks it as “P-core only”? Doesn’t seem hard. I don’t known Linux scheduler internals though.

pantalaimon3y ago

Threads already have an affinity bit mask where you can select which cores they can be scheduled on.

https://man7.org/linux/man-pages/man2/sched_setaffinity.2.ht...

saagarjhaOP3y ago

Right but then you’d just have all processes with that flag all the time.

pantalaimon3y ago

Only if glibc decides to use AVX512 for memset and such. I’m not sure if that makes sense to begin with, but it could also not do that if it detects a heterogeneous CPU.

heavenlyblue3y ago

You don’t have to schedule your thread on another core at all

j / k navigate · click thread line to collapse

0 comments

boardwaalk3y ago

Couldn’t there be some flag on the thread that marks it as “P-core only”? Doesn’t seem hard. I don’t known Linux scheduler internals though.

pantalaimon3y ago

Threads already have an affinity bit mask where you can select which cores they can be scheduled on.

https://man7.org/linux/man-pages/man2/sched_setaffinity.2.ht...

saagarjhaOP3y ago

Right but then you’d just have all processes with that flag all the time.

pantalaimon3y ago

Only if glibc decides to use AVX512 for memset and such. I’m not sure if that makes sense to begin with, but it could also not do that if it detects a heterogeneous CPU.

heavenlyblue3y ago

You don’t have to schedule your thread on another core at all

j / k navigate · click thread line to collapse