Date: Wed, 23 Jan 2019 08:39:41 +0100 (CET) From: Wojciech Puchar <wojtek@puchar.net> To: Mark Saad <nonesuch@longcount.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: CPU Isolation Message-ID: <alpine.BSF.2.20.1901230839300.59235@puchar.net> In-Reply-To: <CAMXt9NbKwZAwv%2BWJ4yqmeMFmX38n=qjUqJSq4kOq2qdNSVEhHg@mail.gmail.com> References: <CAMXt9NbKwZAwv%2BWJ4yqmeMFmX38n=qjUqJSq4kOq2qdNSVEhHg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
man cpuset On Tue, 22 Jan 2019, 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@longcount.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1901230839300.59235>