From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal =?iso-8859-1?Q?Koutn=FD?= Subject: Re: Short process stall after assigning it to a cgroup Date: Wed, 23 Jun 2021 19:28:11 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="iwo5q46b7oRDEl/S" Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1624469293; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=mYyynKwtehNPTyX1THKKb3El0qFbl9kjsXWw3DO0Cyg=; b=ggCdPixjzjfnvYzh8cFPC3mmpsko8L8djdCRmIRn9tB3zoo2F84MzrI5ApxBCpghL1j+6S GY/vZwY1q/UQdJ/4TZBwmoQjJWUExfeYywJ2/1RCJuRhkuZF1MtENMZaPHh22hDeQZxqgk qwvo9Azn0auThexBB0JVarf8/IMRf6g= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1624469293; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=mYyynKwtehNPTyX1THKKb3El0qFbl9kjsXWw3DO0Cyg=; b=ggCdPixjzjfnvYzh8cFPC3mmpsko8L8djdCRmIRn9tB3zoo2F84MzrI5ApxBCpghL1j+6S GY/vZwY1q/UQdJ/4TZBwmoQjJWUExfeYywJ2/1RCJuRhkuZF1MtENMZaPHh22hDeQZxqgk qwvo9Azn0auThexBB0JVarf8/IMRf6g= Content-Disposition: inline In-Reply-To: List-ID: To: Ronny Meeus Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org --iwo5q46b7oRDEl/S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello Ronny. On Mon, Jun 14, 2021 at 05:29:35PM +0200, Ronny Meeus wrote: > All apps are running in the realtime domain and I'm using kernel 4.9 > and cgroup v1. [...] when it enters a full load condition [...] > I start to gradually reduce the budget of the cgroup until the system > is idle enough. Has your application some RT requirements or is there other reason why you use group RT allocations? (When your app seems to require all CPU time, you decide to curb it. And it still fullfills RT requirements?) > But sometimes, immediately after the process assignment, it stops for > a short period (something like 1 or 2s) and then starts to consume 40% > again. What if you reduce cpu.rt_period_us (and cpu.rt_runtime_us proportionally)? (Are the pauses shorter?) Is there any useful info in /proc/$PID/stack during these periods? > Is that expected behavior? Someone with RT group schedulling knowledge may tell :-) HTH, Michal --iwo5q46b7oRDEl/S Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEEoQaUCWq8F2Id1tNia1+riC5qSgFAmDTbycACgkQia1+riC5 qSjuGw/+PwgyMCdN3B3T/DIUA8jgqdahhAhOr6gvKki2T+6nna3+hEHUgxek2IJr hLcLKL6EDyHQDTPi5CuqD/yDmpMePCbZiKbx6TczCk1wlbVAeUrJo5MZmVqqoZX/ +CISMLNWXZ1zdvGB7FXa3yOn10Q99EAwBo8IycXpg8YNMExlboaDpUZNtfjiaQnE +XcXTi1titifBLtV5SPo3EkOkUSivGyQo6vcvWQcEsBO3CHpHK3bJCzxCHlV4hzM LsaYBTs8dmp8Om8BkybbuR61YsghFiZyFULRIDAUfbd3Jt7cLJvdgPdXQL4rJEEy 7mbq2x46n/r8v3m3DR6KLpO+a+OGChxFZFxSGuN0jqA0/ae2sXwetX94mVsml/Zd NOFYv22Hm+yhM5UEQUWBlq6AuvKmgVeuqVBY6JGaKXFq540k8WoERDHQ0vWpyhUv 68WTrcVEE5IWSzZ/SM6sOA8EPf7e5PzvRe9ddCNIKmpOYP7fyIzyVe7v1Fi+QHUf jxaARY1/Dyx84lm4eqLJ6j+038iMDAvP7gX3HG9uOnAJAF7dTGyW4HY3nPm00iyZ FYbx1ZEIFMWKKOXDbxUVopZM5JPdFzF30zq1GXPR0N54IimDNkQEQ1pJjsRAYJn2 LWTq7ed2zVnW/Eb1xM06+kH5d2LgfxzRGxe/XX9d4lL7FKkqEzE= =oi2J -----END PGP SIGNATURE----- --iwo5q46b7oRDEl/S--