From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6552866560629800960 X-Received: by 2002:a1c:6c14:: with SMTP id h20-v6mr187739wmc.13.1525713136327; Mon, 07 May 2018 10:12:16 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:9848:: with SMTP id a69-v6ls1981924wme.0.canary-gmail; Mon, 07 May 2018 10:12:15 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrVr0GzdoZ9YUZcTAHmv1r1ONhezIyumtmBOLgmV5wlAb9MIbztlCErZFreg4G22G0jcUv1 X-Received: by 2002:a1c:3047:: with SMTP id w68-v6mr188430wmw.23.1525713135891; Mon, 07 May 2018 10:12:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525713135; cv=none; d=google.com; s=arc-20160816; b=I+A1l4Kq9h49EXEbKuBrxvGqcsXjVV8g4/ymWGKxVF+e/+Dy6liM6kev63QypOiLLQ Whm/Q5ctnAiXzrPnnx3pq3C/GXiktK49Ax6yxdxqYlDg6fW8rjvfuhfuin3EX/KUnz5p sX+stLi9S1Fl7GAzbfyAeqyvhl0RL3R33D5XNja3kbu3vmzPHa29XnY9Ddot3x0ogawj HhGVu+GztLvqX2GTHqm2Z5v/zCxGnmyLm8o3gV19GObip5VgixWoYIx2dirpV9gXIfG/ CPPM/gEAIOc7sOIdmdZquwkwuQlFJvbMWzGYCAmV/pSd5sGcm0/6G8ryXPfpXXLBAwLe O1eg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=aMtNxpkGXA38etv9QnObBQ2RKgONgl8hdo0F+9Jd57c=; b=ufcEZVyKdbPSC9QU3pP4mPriqllX3ES/pqp9SiscQU27r0OQ9jOdxtFdMATAPa8vFF kWfCM4gekaIkAGD26fgokG5os9T2RyvNiXEeskkY+RpBru/riw4icNKlkq8BYc8kauCj nA4e2I9DIZLfsbkF+SfvR5AwMIQ8E6/EnGF357VZEyNgrPhyyDtXA5RiMwU5spyTd/QY PoiSlJWSKteS1z7t1pA4tdMYK74jUjBjfVARb1TACZ6M4uIRA5rUGJ9p6w9H1dwRkcvw HYi0HTYBE10dlrlEo1+zZd3Vn16eZ2eLQSiCcUrYqzGWJ26q9AOwGangrQzEBbQw6DYt yI2Q== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id w14si186843wmf.1.2018.05.07.10.12.15 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 May 2018 10:12:15 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w47HCF6g021707 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 7 May 2018 19:12:15 +0200 Received: from md1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w47HCEh4015958; Mon, 7 May 2018 19:12:15 +0200 Date: Mon, 7 May 2018 19:12:13 +0200 From: Henning Schild To: Alexander Smirnov Cc: isar-users Subject: Re: [PATCH] isar-bootstrap: Increase cache room Message-ID: <20180507191213.7b68192b@md1pvb1c.ad001.siemens.net> In-Reply-To: <95cd2859-b074-c8a2-4450-cae977ce9846@ilbers.de> References: <20180507154836.25738-1-asmirnov@ilbers.de> <52bdb5c0-5f1f-5efc-5de3-9c5a9253ae3b@ilbers.de> <20180507183151.16ff9387@md1pvb1c.ad001.siemens.net> <95cd2859-b074-c8a2-4450-cae977ce9846@ilbers.de> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: KK1TbH8VT0Vd Am Mon, 7 May 2018 19:48:16 +0300 schrieb Alexander Smirnov : > Hi, > > On 05/07/2018 07:31 PM, Henning Schild wrote: > > Am Mon, 7 May 2018 18:57:36 +0300 > > schrieb Alexander Smirnov : > > > >> On 05/07/2018 06:48 PM, Alexander Smirnov wrote: > >>> According to the man page for 'apt.conf', there are three > >>> variables: > >>> - Cache-Start: initial size of mmap cache room > >>> - Cache-Grow: gap for dynamic mmap cache growth > >>> - Cache-Limit: maximal cache size after growth > >>> > >>> If dynamic resize of mmap region is not avaialbe, the apt uses > >>> pre-allocated Cache-Start room [1] for mmap file. > >>> > >>> Building Isar on one of the Debian host with kernel 3.4, I got the > >>> following problem for 'qemuarm64-stretch' configuration: > >>> > >>> 8<-- > >>> Hit:1 http://security.debian.org stretch/updates InRelease > >>> Ign:2 http://ftp.de.debian.org/debian stretch InRelease > >>> Hit:3 http://ftp.de.debian.org/debian stretch-updates InRelease > >>> Hit:4 http://ftp.de.debian.org/debian stretch Release > >>> E: Dynamic MMap ran out of room. Please increase the size of > >>> APT::Cache-Start. Current value: 25165824. (man 5 apt.conf) qemu: > >>> uncaught target signal 11 (Segmentation fault) - core dumped > >>> Segmentation fault 8<-- > >>> > >>> I have no information, why exactly the room could not be re-sized > >>> on this system, but it would be better to increase the initial > >>> room size for apt. This patch increases the default apt cache > >>> twice. > >> > >> 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657085 > >> > >> Missed :-( > > > > What is your conclusion from that link and what does it mean for the > > patch? > > > > This just the information I found about dynamic cache increasing. > Sometimes it could not work. Another fact is that increasing of > Cache-Limit doesn't help, so seems that mremap really doesn't work. > > > I do not like adding magic numbers and changing the default config, > > especially if the whole reason is to work around a problem only > > found on outdated build hosts (3.4 really?) > > I'm not 100% sure that kernel 3.4 is the source of the problem. Tried > to investigate, but for now without results. > > But if you try to google line: > > E: Dynamic MMap ran out of room. Please increase the size of > APT::Cache-Start > > There will be tons of search results, so such problem occurred not > only on my host. > > > The man page says: > > ...on systems with a lot of configured sources it should be > increased... > > so for me it makes sense to increase this room even if there is only > one problem report. It doesn't break anything. Oh yes it breaks the fact that we do not need to care about the value. If you hardcode one today you might be setting half the default after the next apt-update. ... because it is a magic number and not set(get()*2) > We can't require Isar users to always have up-to-dated host systems. > If this patch makes all Isar users with old kernels happy, it's > probably good for Isar in general :-) Sure, but there is a cost ... see previous point. > > > > If this patch needs to go in, it is missing the cleanup step. > > > > Sorry, what do you mean here by cleanup step? Sorry, misread the patch. I thought it placed a file in the rootfs. Henning > Alex > > > Henning > > > >>> Signed-off-by: Alexander Smirnov > >>> --- > >>> meta/recipes-core/isar-bootstrap/isar-bootstrap.bb | 4 +++- > >>> 1 file changed, 3 insertions(+), 1 deletion(-) > >>> > >>> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb > >>> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb index > >>> a38dd88..4cdefaa 100644 --- > >>> a/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb +++ > >>> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb @@ -187,7 > >>> +187,9 @@ do_apt_update() { > >>> E="${@bb.utils.export_proxies(d)}" > >>> export DEBIAN_FRONTEND=noninteractive > >>> - sudo -E chroot "${ROOTFSDIR}" /usr/bin/apt-get update -y > >>> + sudo -E chroot "${ROOTFSDIR}" /usr/bin/apt-get update -y \ > >>> + -o > >>> APT::Cache-Start=50331648 + > >>> sudo -E chroot "${ROOTFSDIR}" /usr/bin/apt-get dist-upgrade > >>> -y \ -o Debug::pkgProblemResolver=yes > >>> } > >>> > >> > > >