From owner-freebsd-bugs@freebsd.org Mon Sep 16 05:25:39 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 78574F32D8 for ; Mon, 16 Sep 2019 05:25:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46WvpW2YnWz47tt for ; Mon, 16 Sep 2019 05:25:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 51221F32D5; Mon, 16 Sep 2019 05:25:39 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 50DDAF32D4 for ; Mon, 16 Sep 2019 05:25:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46WvpW1Xggz47tm for ; Mon, 16 Sep 2019 05:25:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1252F1B8E4 for ; Mon, 16 Sep 2019 05:25:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x8G5PcqN056507 for ; Mon, 16 Sep 2019 05:25:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8G5PchK056506 for bugs@FreeBSD.org; Mon, 16 Sep 2019 05:25:38 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 240051] top Reports Incorrect Swap File Size Date: Mon, 16 Sep 2019 05:25:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: jlmales@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Sep 2019 05:25:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240051 --- Comment #2 from John --- (In reply to ota from comment #1) As noted in initial bug report htop and swapinfo both report the correct sw= ap file size. top does not report the correct swap file size at something less than what is allocated for swap file size. That is the issue. Further the amount of RAM installed does not determine what the reported si= ze of the swap file or sum of multiple swap files is. Both swapinfo and htop report the correct swap file size. top does not report the correct swap fi= le size. Therefore the issue is top failing to correctly report the swap file size that has no bearing on the amount of ram installed. Swap file was sized during FreeBSD install to accommodate short term and lo= ng term RAM upgrades. In theory there is no restriction on RAM size as function to determine swap file size that can be allocated for any OS. This includes IBM Mainframes t= hat have used Virtual Memory since the 1970s and therefore have used swap files= as a result since the 1970s. In practice there may be limits simply due to extent of swap file/RAM page thrashing/faults per second an OS can incur that is system/application spec= ific mix/active/activity and/or disk space wasted that will not be used for swap= or not used for swap much of the time. System planning and testing enable the swap file size and usage characterizations to be calculated. The amount of swap space defined during an install does not always mean the OS calculated swap file size is taken as at time of install. The OS install calculated default swap file size cannot take into account future system upgrades, nor characterization usage patterns of system/applications of the swap file. The amount of RAM currently install on the system is provided in the information when the initial bug report was made. I have worked with Virtual Memory based OSs since the 1970s. I have lots of experience with Virtual Memory and swap file space allocations/characterizations on IBM Mainframes as well as Unix since the e= arly 1990s (SunOS, AIX, System V, Linux, et al) based systems and some Unix experience as early as the mid 1970s. --=20 You are receiving this mail because: You are the assignee for the bug.=