From owner-freebsd-current@freebsd.org Mon Mar 12 04:01:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E0FDF464AD for ; Mon, 12 Mar 2018 04:01:29 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-pl0-x242.google.com (mail-pl0-x242.google.com [IPv6:2607:f8b0:400e:c01::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87AA38DDC3 for ; Mon, 12 Mar 2018 04:01:28 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: by mail-pl0-x242.google.com with SMTP id u13-v6so8650478plq.1 for ; Sun, 11 Mar 2018 21:01:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jroberson-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=7XlaJmsWs5aJf3dgFjjeQMYSB71hZmdnhQV8zqWdYbo=; b=o0qFeaoOlSevvRbXG9DFaLrP/4L4XeLe/hA0H7op7ht59753ybGnUBRK1tCpDlPy5+ H3O2mi+R6a5lswUbKhH+22SEJNnsyNRKLEESZhFiOE3b/RzUOpq/MwxFcSIn1Xj/IMgO L85VSQq2IFO/V5fl1Dw+cCBtlW1AHcN7/qAvGwbmwvcUbV5ywdn1GCf/8NkmH0Ej3u0c iXY+AsFP1hk1160Q2MShvtecWTisfYDw2L7JGgtBwTWsZPPej9UsCQgANQQdnf7vSa2M BF11D9CDwvh34hYcm9UolggQb6O8uSR0v1e9PlNIEmqe5cYCdpYMmd+ztdVtrzCfgy8S 66HA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=7XlaJmsWs5aJf3dgFjjeQMYSB71hZmdnhQV8zqWdYbo=; b=aRwJG7NqthSitqota8u74EHvakGqFBXE2impldUVFKK/qBY7kDIvoSbBIoYxkTqvcN nE3uhPmG0Al9Fxu8Ui/f8B+OVMGrE9RWwi3w80yDiAfgdHj7xm/hOv3saemS39tIAvKJ pafDrlvqTpzOHGgGWcEs8YUuBs3FOWdAG5Nk/MWLuobbHBHmTvjTWCYuYbi/9Fxi4/qz g+7iVPIakG6KV3hSIdcKcbJKL4Rw6W9boF2rDUTYQo9ZRsBzaZxihujdGRKhRHcaQ0lm W3D57Feh/3tHbwOs5q2olhPoP7eA2aGVD94EIty9ftim+sBjGGRLyQezPaop0aKEC/T4 rK9A== X-Gm-Message-State: AElRT7HBCIYltCJp1YnLjtieL6c5dTIFRA+n9hAvMetpKiVXYvDnT5hV XxdKC8qwCZShRXeQZO48k6OzTQ== X-Google-Smtp-Source: AG47ELvgZOCYMmodciiOs9KYekzgZonqI6WGqhNvjxbASuFHnCRE8fyAMotYAxkTBiOHejZblFBX6w== X-Received: by 2002:a17:902:22f:: with SMTP id 44-v6mr6684020plc.377.1520827287708; Sun, 11 Mar 2018 21:01:27 -0700 (PDT) Received: from rrcs-66-91-135-210.west.biz.rr.com (rrcs-66-91-135-210.west.biz.rr.com. [66.91.135.210]) by smtp.gmail.com with ESMTPSA id f82sm14440321pfd.175.2018.03.11.21.01.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Mar 2018 21:01:27 -0700 (PDT) Date: Sun, 11 Mar 2018 18:00:35 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Mark Millard cc: freebsd-current@freebsd.org, "O. Hartmann" Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2018 04:01:29 -0000 On Sun, 11 Mar 2018, Mark Millard wrote: > As I understand, O. Hartmann's report ( ohartmann at walstatt.org ) in: > > https://lists.freebsd.org/pipermail/freebsd-current/2018-March/068806.html > > includes a system with a completely non-ZFS context: UFS only. Quoting that part: > >> This is from a APU, no ZFS, UFS on a small mSATA device, the APU (PCenigine) works as a >> firewall, router, PBX): >> >> last pid: 9665; load averages: 0.13, 0.13, 0.11 >> up 3+06:53:55 00:26:26 19 processes: 1 running, 18 sleeping CPU: 0.3% user, 0.0% >> nice, 0.2% system, 0.0% interrupt, 99.5% idle Mem: 27M Active, 6200K Inact, 83M >> Laundry, 185M Wired, 128K Buf, 675M Free Swap: 7808M Total, 2856K Used, 7805M Free >> [...] >> >> The APU is running CURRENT ( FreeBSD 12.0-CURRENT #42 r330608: Wed Mar 7 16:55:59 CET >> 2018 amd64). Usually, the APU never(!) uses swap, now it is starting to swap like hell >> for a couple of days and I have to reboot it failty often. > > Unless this is unrelated, it would suggest that ZFS and its ARC need not > be involved. > > Would what you are investigating relative to your "NUMA and concurrency > related work" fit with such a non-ZFS (no-ARC) context? I think there are probably two different bugs. I believe the pid controller has caused the laundry thread to start being more aggressive causing more pageouts which would cause increased swap consumption. The back-pressure mechanisms in arch should've resolved the other reports. It's possible that I broke those. Although if the reports from 11.x are to be believed I don't know that it was me. It is possible they have been broken at different times for different reasons. So I will continue to look. Thanks, Jeff > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) >