From nobody Sun Aug 14 17:31:45 2022 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M5Pbx5QC8z4ZsZS for ; Sun, 14 Aug 2022 17:31:57 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M5Pbx4zfrz41tb for ; Sun, 14 Aug 2022 17:31:57 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1660498317; h=from:from:reply-to:subject:subject: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=2Qmim+j7DJm0ahVbFy5nEe+FoZkYDh+1aj/wM17XQ80=; b=JQ8UJ/GwvtJGmQrXTfUirlei+vzBZQRuT5EMHm4d9TJXhJ/cJXdaTR87Fz2GNdEyrlcyeo ZGlAr01tNPjoBiKGTpgaqu4ZRRJCDgsc3Ed1Y0UjwswtZ197M6ua/OMoehiYilLxuvMxc9 ZEsebLaForQbrAraolXT4RRdsIsbWEVfIte9+Il98d2JgRlIKgxkseXtmOI0P7xf5bzoO4 Aote/ODmyVxYur1odm9VhwabZuJuzYKDrGTBFti6bR4EWTM9dPe+8hM5U/cEDxVR99L1Np E+4e3o9P2mjCZUNwp0Y7wdITsTNuB6h7G6TmuWYmOuK7joXMClVvhSHdmgBssg== Received: from mail-ua1-f42.google.com (mail-ua1-f42.google.com [209.85.222.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4M5Pbx3xxDz1CXk for ; Sun, 14 Aug 2022 17:31:57 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-ua1-f42.google.com with SMTP id s18so2138297uac.10 for ; Sun, 14 Aug 2022 10:31:57 -0700 (PDT) X-Gm-Message-State: ACgBeo3/FxzRdGLX1m9HC5zPRyEowSTvT1gUPC3YNI8p/G6o3UbpmOaT RVDBrxpfTQDc/0Q45mSmWIX40SXSths5HMVE0wU= X-Google-Smtp-Source: AA6agR7RM4z9TRa1JOV74eHXkbB0bEPFSa1VROa0MBnU3mOcpyVzpv2/K5Z0XH0EnKoBBIF15u0x8foDvXGETSU6PCU= X-Received: by 2002:a9f:358c:0:b0:387:9de3:6c8a with SMTP id t12-20020a9f358c000000b003879de36c8amr4960435uad.94.1660498317034; Sun, 14 Aug 2022 10:31:57 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <1D4C14BD-8955-4B86-9C99-3E58D7603122.ref@yahoo.com> <1D4C14BD-8955-4B86-9C99-3E58D7603122@yahoo.com> <7CDC63F3-8B68-420E-8012-B1692667E293@yahoo.com> <21FC1F5E-240E-4A8C-A5D2-6B73494026C0@yahoo.com> In-Reply-To: <21FC1F5E-240E-4A8C-A5D2-6B73494026C0@yahoo.com> From: Nuno Teixeira Date: Sun, 14 Aug 2022 18:31:45 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Resolved: devel/llvm13 build: "ninja: build stopped: subcommand failed" To: Mark Millard Cc: FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000564d2405e636e40f" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1660498317; h=from:from:reply-to:subject:subject: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=2Qmim+j7DJm0ahVbFy5nEe+FoZkYDh+1aj/wM17XQ80=; b=Iab3wj0X9pCPNiGty1GDe3Pekh9KW8Pa/BiEIzaEyyYcOEwRupdu+vHIKuOvK0vp0EMrfc 55bod2/RmG32fXEMJsEetbCRO/llxd99Vqp9ByaQhwuA1CvSm+5FtTfspKLEcWJzu67Lo7 hZsUgersROmz/avzzo8LecYibnjnapeZPrdi8yN4hPoMLdeFu5QHeOWdgVNCwkMBX6U9RW I4Qc+Z1njWWHI7wBNREq6WNaHGSWDuE5GyU5wz9ADpsUkFoLHbBhw0CWZdm31fjL7wLpJi 3rpTHYuSedS2hp5rSypdmjhFGATeROrx+7Gg2wpCVkygxGLSU9cNVYHS4RQFSw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1660498317; a=rsa-sha256; cv=none; b=InNnJbSSHZn4AP3YTqAumxmbDvwGN0pF+VAk8HIO0tzV8DNcGtwVyoLIRKkhqLY/YEasIY JEraPvn7fmyVOeTZGL1hh1yd1KGwlSD1K1PyBiPKNByLyFlVze5UG9R6H6wAH//kYmbqy+ leTBN01y/eNPILIEwRweitu23RjC+3hjVrVLEpblJ4+GnGl/IzIJXnew7fWS4SY0WCIfll M3UYa0yXCD6w0+dcgBakcX1+xAAgHYcJ+zt1Zd5/N+ewXwLfrZPB8qPaHsKaC4DAxGGRK6 bjwH6IgnAO/vQqHlzNi9rtQtz8MU8tawNBVQYacFzbtKQlYYMNS43MKCecis1g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --000000000000564d2405e636e40f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ok, I will avoid a swap file. My actual config shows: `swapinfo`: --- Device 1K-blocks Used Avail Capacity /dev/nvd0p2 4194304 6036 4188268 0% --- and `cat /etc/fstab`: --- # Device Mountpoint FStype Options Dump Pass# /dev/nvd0p1 /boot/efi msdosfs rw 2 2 /dev/nvd0p2 none swap sw 0 0 --- Any clues how do I do this? Mark Millard escreveu no dia domingo, 14/08/2022 =C3=A0= (s) 18:21: > On 2022-Aug-14, at 10:15, Nuno Teixeira wrote: > > > I use ZFS. > > > > I will follow your recomendations and use a swap of 64GB and then test > it again. > > > > In the meanwhile I will take a look at freebsd docs to see how do I > increase swap, by adding a new swap file or resize actual one if possible= . > > I recommend never using a swap file, only swap partition(s), in order > to avoid deadlocks and such: > > On 2017-Feb-13, at 7:20 PM, Konstantin Belousov > wrote > on the freebsd-arm list: > > . . . > > swapfile write requires the write request to come through the filesystem > write path, which might require the filesystem to allocate more memory > and read some data. E.g. it is known that any ZFS write request > allocates memory, and that write request on large UFS file might require > allocating and reading an indirect block buffer to find the block number > of the written block, if the indirect block was not yet read. > > As result, swapfile swapping is more prone to the trivial and unavoidable > deadlocks where the pagedaemon thread, which produces free memory, needs > more free memory to make a progress. Swap write on the raw partition ove= r > simple partitioning scheme directly over HBA are usually safe, while e.g. > zfs over geli over umass is the worst construction. > > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > --=20 Nuno Teixeira FreeBSD Committer (ports) --000000000000564d2405e636e40f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ok, I will avoid a swap file.

My actual config shows:
`swapinfo`:
---
Device =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01K-blocks =C2=A0 =C2=A0 Used =C2= =A0 =C2=A0Avail Capacity
/dev/nvd0p2 =C2=A0 =C2=A0 =C2=A0 4194304 =C2=A0= =C2=A0 6036 =C2=A04188268 =C2=A0 =C2=A0 0%
---
and `ca= t /etc/fstab`:
---
# Device =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0Mountpoint =C2=A0 =C2=A0 =C2=A0FStype =C2=A0Opt= ions =C2=A0 =C2=A0 =C2=A0 =C2=A0 Dump =C2=A0 =C2=A0Pass#
/dev/nvd0p1 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /boot/efi =C2=A0 =C2=A0 =C2=A0 msdos= fs rw =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02 =C2=A0 =C2=A0 =C2= =A0 2
/dev/nvd0p2 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 none =C2=A0 = =C2=A0swap =C2=A0 =C2=A0sw =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= 0 =C2=A0 =C2=A0 =C2=A0 0
---

Any clues h= ow do I do this?

Mark Millard <marklmi@yahoo.com> escreveu no dia domingo, 14/08/2022 =C3=A0(s) 18= :21:
On 2022-Aug= -14, at 10:15, Nuno Teixeira <eduardo@freebsd.org> wrote:

> I use ZFS.
>
> I will follow your recomendations and use a swap of 64GB and then test= it again.
>
> In the meanwhile I will take a look at freebsd docs to see how do I in= crease swap, by adding a new swap file or resize actual one if possible.
I recommend never using a swap file, only swap partition(s), in order
to avoid deadlocks and such:

On 2017-Feb-13, at 7:20 PM, Konstantin Belousov <kostikbel at gmail.com> w= rote
on the freebsd-arm list:

. . .

swapfile write requires the write request to come through the filesystem write path, which might require the filesystem to allocate more memory
and read some data. E.g. it is known that any ZFS write request
allocates memory, and that write request on large UFS file might require allocating and reading an indirect block buffer to find the block number of the written block, if the indirect block was not yet read.

As result, swapfile swapping is more prone to the trivial and unavoidable deadlocks where the pagedaemon thread, which produces free memory, needs more free memory to make a progress.=C2=A0 Swap write on the raw partition = over
simple partitioning scheme directly over HBA are usually safe, while e.g. zfs over geli over umass is the worst construction.



=3D=3D=3D
Mark Millard
marklmi at yahoo.com



--
Nun= o Teixeira
FreeBSD Committer (ports)
--000000000000564d2405e636e40f--