From owner-freebsd-fs@freebsd.org  Thu Dec  7 22:55:58 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91EC4E937AB
 for <freebsd-fs@mailman.ysv.freebsd.org>; Thu,  7 Dec 2017 22:55:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8039B7A846
 for <freebsd-fs@FreeBSD.org>; Thu,  7 Dec 2017 22:55:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vB7MtwmB052829
 for <freebsd-fs@FreeBSD.org>; Thu, 7 Dec 2017 22:55:58 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 224080] ZFS: "arc_dnlc_evicts_thr" + "arc_reclaim_thread" -
 high CPU load during poudriere build...
Date: Thu, 07 Dec 2017 22:55:58 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jeff@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-224080-3630-0I0d7pAfMe@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224080-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-224080-3630@https.bugs.freebsd.org/bugzilla/>
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-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Dec 2017 22:55:58 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224080

--- Comment #26 from Jeff Roberson <jeff@FreeBSD.org> ---
We can use the new uma limit facility.  I can produce a diff in a couple of
hours.  This is essentially the same thing that kmem_map_free does however:

static int
sysctl_kmem_map_free(SYSCTL_HANDLER_ARGS)
{
        u_long size, limit;

        /* The sysctl is unsigned, implement as a saturation value. */
        size =3D uma_size();
        limit =3D uma_limit();
        if (size > limit)
                size =3D 0;
        else
                size =3D limit - size;
        return (sysctl_handle_long(oidp, &size, 0, req));
}

We should make a uma accessor to compute this.

--=20
You are receiving this mail because:
You are the assignee for the bug.=