Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Jan 2019 00:01:38 +0300
From:      "Andrey V. Elsukov" <bu7cher@yandex.ru>
To:        Mark Saad <nonesuch@longcount.org>
Cc:        FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: CPU Isolation
Message-ID:  <e1997066-b924-39ff-af11-7d55dc95d8b0@yandex.ru>
In-Reply-To: <CAMXt9NYmKTtNggSVV1bxZsr0L1HWJN1KHRG6bEp_JLyBNAN8PA@mail.gmail.com>
References:  <CAMXt9NbKwZAwv%2BWJ4yqmeMFmX38n=qjUqJSq4kOq2qdNSVEhHg@mail.gmail.com> <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> <CAMXt9NYmKTtNggSVV1bxZsr0L1HWJN1KHRG6bEp_JLyBNAN8PA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--0gOaGfzy4uR0QCkjOcUTlO6hoGKwlijVN
Content-Type: multipart/mixed; boundary="1Vc4IEhZovUVfTQtXqpfaonPHZTy0goIz";
 protected-headers="v1"
From: "Andrey V. Elsukov" <bu7cher@yandex.ru>
To: Mark Saad <nonesuch@longcount.org>
Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>
Message-ID: <e1997066-b924-39ff-af11-7d55dc95d8b0@yandex.ru>
Subject: Re: CPU Isolation
References: <CAMXt9NbKwZAwv+WJ4yqmeMFmX38n=qjUqJSq4kOq2qdNSVEhHg@mail.gmail.com>
 <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru>
 <CAMXt9NYmKTtNggSVV1bxZsr0L1HWJN1KHRG6bEp_JLyBNAN8PA@mail.gmail.com>
In-Reply-To: <CAMXt9NYmKTtNggSVV1bxZsr0L1HWJN1KHRG6bEp_JLyBNAN8PA@mail.gmail.com>

--1Vc4IEhZovUVfTQtXqpfaonPHZTy0goIz
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 28.01.2019 22:25, Mark Saad wrote:
> 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.

As r331723 says, now kernel threads belong to cpuset #2, all other
processes belong to cpuset 1. So, you can try to use commands:
Limit all userlevel application to use only CPU cores 0-4:
 # cpuset -s 1 -l 0-4
Limit kernel level threads to use CPU only CPU cores 0-4:
 # cpuset -s 2 -l 0-4
and then dedicate CPUs 5-7 for your application with pid PID
 # cpuset -l 5-7 -p PID

--=20
WBR, Andrey V. Elsukov


--1Vc4IEhZovUVfTQtXqpfaonPHZTy0goIz--

--0gOaGfzy4uR0QCkjOcUTlO6hoGKwlijVN
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlxPbbIACgkQAcXqBBDI
oXqM3Af+JVauRTNAb1zdf8msElT5R40HUAslbM3/RTIrS9bzLL1K3yRy/72rSXOY
LSLtWRTOWQQqkQ2qd2NxdFbiIzGINAuCJ8GJO+SKARRIsabWPOsXWw1z9mVl5hdi
5VbumtDHs+T3LqzRr2024KUF3GV+yNeSjUEW9Yp8H9JU9xWuOuicOcNMGH33OS/S
+52Az2l+s062kKcZwrypI9X+qg5PyX380C5A/0iO/vcHOfQshD98hRe+bjWpDuiJ
sNyJXucXtyIs37WRe8xmyK7gec4/LZ8ivWpHxmdJcHu2Dy33EardlgNBOfJLVTQ4
cVUfbAfl5pp6PaxgQKGrhrwl19Wqxw==
=PqgO
-----END PGP SIGNATURE-----

--0gOaGfzy4uR0QCkjOcUTlO6hoGKwlijVN--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e1997066-b924-39ff-af11-7d55dc95d8b0>