On Di, 03.09.19 19:49, Alexey Perevalov (a.pereva...@samsung.com) wrote:
> Hello Michal,
>
> Thank you for response!
>
> On 9/3/19 6:03 PM, Michal Koutný wrote:
> > Hello Alexey.
> >
> > On Fri, Aug 30, 2019 at 01:21:50PM +0300, Alexey Perevalov
> > wrote:
> > > [...]
> > > The question is:
Hello Michal,
Thank you for response!
On 9/3/19 6:03 PM, Michal Koutný wrote:
Hello Alexey.
On Fri, Aug 30, 2019 at 01:21:50PM +0300, Alexey Perevalov
wrote:
[...]
The question is: changing CPUAffinity property (cpuset.cpus) is not yet
allowed in systemd API, right? Is it planned?
Note
Hello Alexey.
On Fri, Aug 30, 2019 at 01:21:50PM +0300, Alexey Perevalov
wrote:
> [...]
> The question is: changing CPUAffinity property (cpuset.cpus) is not yet
> allowed in systemd API, right? Is it planned?
Note that CPUAffinity= uses the mechanism of sched_setaffinity(2) which
is
Hi,
I found when we set CPUAffinity in unit file or property by DBUS we need
to restart daemon. It's strange because CPUShares could be applied w/o
restarting daemon. So after systemctl set-property my-slice CPUShares=50
I see changes in cgroup fs immediately, but CPUAffinity is not in the
