From: Conor Dooley <conor.dooley@microchip.com>
To: Celeste Liu <coelacanthushex@gmail.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org>,
Anup Patel <anup@brainfault.org>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Russell King <linux@armlinux.org.uk>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Tony Lindgren <tony@atomide.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<loongarch@lists.linux.dev>, <linux-sh@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rpi-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] riscv: defconfig: drop RT_GROUP_SCHED=y
Date: Mon, 9 Sep 2024 14:06:48 +0100 [thread overview]
Message-ID: <20240909-arguable-detection-02445bd1cc89@wendy> (raw)
In-Reply-To: <9e364ae4-dc2c-4efa-8611-462218402a5d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2726 bytes --]
On Mon, Sep 09, 2024 at 08:14:16PM +0800, Celeste Liu wrote:
> On 2024-09-09 19:53, Conor Dooley wrote:
>
> > On Fri, Aug 23, 2024 at 01:43:26AM +0800, Celeste Liu wrote:
> >> Commit ba6cfef057e1 ("riscv: enable Docker requirements in defconfig")
> >> introduced it because of Docker, but Docker has removed this requirement
> >> since [1] (2023-04-19).
> >>
> >> For cgroup v1, if turned on, and there's any cgroup in the "cpu" hierarchy it
> >> needs an RT budget assigned, otherwise the processes in it will not be able to
> >> get RT at all. The problem with RT group scheduling is that it requires the
> >> budget assigned but there's no way we could assign a default budget, since the
> >> values to assign are both upper and lower time limits, are absolute, and need to
> >> be sum up to < 1 for each individal cgroup. That means we cannot really come up
> >> with values that would work by default in the general case.[2]
> >>
> >> For cgroup v2, it's almost unusable as well. If it turned on, the cpu controller
> >> can only be enabled when all RT processes are in the root cgroup. But it will
> >> lose the benefits of cgroup v2 if all RT process were placed in the same cgroup.
> >>
> >> Red Hat, Gentoo, Arch Linux and Debian all disable it. systemd also doesn't
> >> support it.[3]
> >>
> >> [1]: https://github.com/moby/moby/commit/005150ed69c540fb0b5323e0f2208608c1204536
> >> [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1229700
> >> [3]: https://github.com/systemd/systemd/issues/13781#issuecomment-549164383
> >>
> >> Fixes: ba6cfef057e1 ("riscv: enable Docker requirements in defconfig")
> >
> > I don't think this fixes tag is suitable, the commit you cite in
> > moby/docker is a year younger than the one in the fixes tag, so it was
> > correct at the time it was written. I think the fixes tag should just be
> > removed, since that commit was not wrong. Or am I missing something?
>
> The Docker commit I cited introduce the fix, not the bug. So it should be later
> than commit in fixes tag, otherwise Heinrich Schuchardt won't pick the wrong
> config from upstream.
>
> Timeline is:
> 1) 2015-06-19 Qiang Huang introduce RT_GROUP_SCHED check in Docker.[1]
> 2) 2022-06-08 Heinrich Schuchardt pick this to defconfig in commit
> in fixes tag.
> 3) 2023-04-19 Florian Schmaus remove this requirement from Docker in
> commit I cited.
Yes, this is the way I understood things to be. IOW, when Heinrich wrote
ba6cfef057e1 ("riscv: enable Docker requirements in defconfig"), it was
a requirement for docker. The requirement later being removed doesn't
make his patch incorrect, which is why I don't think this is a fix.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-09 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 17:43 [PATCH v2 0/4] defconfig: drop RT_GROUP_SCHED=y Celeste Liu
2024-08-22 17:43 ` [PATCH v2 1/4] riscv: " Celeste Liu
2024-09-09 11:53 ` Conor Dooley
2024-09-09 12:14 ` Celeste Liu
2024-09-09 13:06 ` Conor Dooley [this message]
2024-09-09 13:14 ` Celeste Liu
2024-09-10 12:57 ` Celeste Liu
2024-09-09 13:14 ` Heinrich Schuchardt
2024-08-22 17:43 ` [PATCH v2 2/4] loongarch: " Celeste Liu
2024-08-22 17:43 ` [PATCH v2 3/4] sh: defconfig: drop RT_GROUP_SCHED=y from sdk7786/urquell Celeste Liu
2024-08-22 17:43 ` [PATCH v2 4/4] arm: defconfig: drop RT_GROUP_SCHED=y from bcm2835/tegra/omap2plus Celeste Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240909-arguable-detection-02445bd1cc89@wendy \
--to=conor.dooley@microchip.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chenhuacai@kernel.org \
--cc=coelacanthushex@gmail.com \
--cc=dalias@libc.org \
--cc=florian.fainelli@broadcom.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=guoren@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=jonathanh@nvidia.com \
--cc=kernel@xen0n.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=loongarch@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).