Also, you can configure the kernel at boot to exclude certain cpus from the OS
completely so no process can interfere with them - BUT - processes/threads can
still be moved to these isolated cpus using setsched().
> On Sep 27, 2024, at 10:34 AM, robert engels wrote:
>
> What you want to do is
What you want to do is start the process with a cset to restrict the cores it
can use - then use the setsched to move certain threads to cores that have been
excluded.
> On Sep 27, 2024, at 10:26 AM, 'TheDiveO' via golang-nuts
> wrote:
>
> Are you running this on a multi-core? Your non-fifo t
Seems to have changed, as there have been quite some more kthread-types
sprung up. Oh, you're reminding me ask the OP a question just to be sure...
On Friday, September 27, 2024 at 5:53:33 PM UTC+2 robert engels wrote:
> I am not sure that is true unless things have changed. You can configure
>
I am not sure that is true unless things have changed. You can configure the
interrupt/kernel handlers to run on specific cpus and keep other cpus and their
caches completely isolated. There was an issue at one point with clock timings
but as I recall it was resolved (it’s been several years so
you need to keep a bunch of per-cpu ("per-core") kernel threads and you
need to make sure not to starve them, but for a short test that's okay. oh,
and don't have any processes running that use io uring...
On Friday, September 27, 2024 at 5:37:53 PM UTC+2 robert engels wrote:
> Also, you can co
Hi gophers,
I'm doing a research on how to prioritise some goroutines over others.So I
can allocate more CPU resource to more important part of the program.
I try to do it by calling runtime.LockOSThread to assign the goroutine
needs to be prioritise to a designated OS thread, and unix.SchedSetA
