CPU Isolation

[Babak Farrokhi]

AFAIK there is no way to do it pre-boot. To do the isolation post-boot your best bet is cpuset(1) (with which I could not totally isolate cpu cores as dedicated application cores).


On 22 Jan 2019, at 19: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?
>
> -- 
> mark saad | nonesuch at longcount.org
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20190128/9ab82dc3/attachment.sig>