undefined | Better HN

0 pointssaagarjha4y ago0 comments

Presumably the AVX-512 code is something on your hot path, so I’m not sure waiting for a signal to reschedule the work is something you would want.

0 comments

You reschedule it only once so it doesn’t matter

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…

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.

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

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

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

j / k navigate · click thread line to collapse

You reschedule it only once so it doesn’t matter

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…

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.

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

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

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

j / k navigate · click thread line to collapse