CPU Isolation

[Mark Saad]

All
  Thanks for the replies, I had experimented with the init script
method but ; I kept thinking that I was doing this wrong. I think that
adding a loader option to
isolate cpus from the scheduler would be useful; but I have no idea
how to get there.  My current plans are to setup init to use cpus 0-4
and to use 5-7 for my applications
and see how it goes. The other test I want to try is to run some
kernel threads on dedicated cores. Let me try to break stuff now.

On Mon, Jan 28, 2019 at 7:20 AM Andrey V. Elsukov <bu7cher at yandex.ru> wrote:
>
> On 22.01.2019 21:29, Mark Saad wrote:
> > All
> >  I am looking to setup a 12-STABLE box in a way that is similar to a
> > CentOS server I am running.
> > That server is setup using the boot option isocpus, to remove
> > cores/cpus from the kernel scheduler at boot.  What I want to try on
> > 12-STABLE is to set aside some cores to run process and some kernel
> > threads that will only always run on a dedicated core with out the
> > chance for being preempted / interrupted by something else on that
> > core / cpu . What I do not see is a way to  evict processes off a
> > running cpu post boot or a way to isolate them preboot. Am  I missing
> > something?
> >
>
> After r331723 it is possible to make such separation after boot using
> cpuset(8). If you need this a bit early, you need to modify sbin/init.
>
> --
> WBR, Andrey V. Elsukov
>


-- 
mark saad | nonesuch at longcount.org