From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38055) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eS39f-0006G8-56 for guix-patches@gnu.org; Thu, 21 Dec 2017 10:53:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eS39a-0004yf-7c for guix-patches@gnu.org; Thu, 21 Dec 2017 10:53:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:37625) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eS39a-0004yY-3k for guix-patches@gnu.org; Thu, 21 Dec 2017 10:53:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eS39Z-0000Xw-T7 for guix-patches@gnu.org; Thu, 21 Dec 2017 10:53:01 -0500 Subject: [bug#29409] Remove hugetlb control group on ARM32. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <877euhtjkj.fsf@gmail.com> <87ind19pok.fsf@gmail.com> <20171221095752.1a018320@scratchpost.org> Date: Thu, 21 Dec 2017 16:52:07 +0100 In-Reply-To: <20171221095752.1a018320@scratchpost.org> (Danny Milosavljevic's message of "Thu, 21 Dec 2017 09:57:52 +0100") Message-ID: <87tvwk3wpk.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Danny Milosavljevic Cc: 29409@debbugs.gnu.org Hi, Danny Milosavljevic skribis: > On Wed, 20 Dec 2017 20:15:07 +0100 > Mathieu Othacehe wrote: > >> I'm not sure what do about, a workaround could be the ugly hack >> attached, WDYT ? > > I researched cgroups a bit and it seems that /sys/fs/cgroup/hugetlb is fo= r configuration of hugetlb and that cgroups themselves don't require hugetl= b - and neither does elogind. Indeed. So actually we can probably remove it altogether. We could simply do that and keep the definition around for when we need it. Thoughts? > We could use (file-exists? "/proc/sys/vm/nr_hugepages") in order to test = for hugetlb support. The proc filesystem is already mounted at this point. Currently we can=E2=80=99t easily introduce special conditions for file sys= tem mounts. > Alternatively, it would be possible to use (needed-for-boot? #f) for the = hugetlb cgroup file-system. In that case, maybe failure isn't so bad. I d= idn't test that, however. =E2=80=98need-for-boot?=E2=80=99 tells whether the file system should be mo= unted from the initrd or after PID=C2=A01 has been started, so it doesn=E2=80=99t help= in this case (it=E2=80=99s already #f I think.) Ludo=E2=80=99.