From owner-freebsd-current@freebsd.org Mon Jan 2 15:55:46 2017 Return-Path: Delivered-To: freebsd-current@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 0DEDBC9C373 for ; Mon, 2 Jan 2017 15:55:46 +0000 (UTC) (envelope-from jonathan.robert.anderson@gmail.com) Received: from mail-io0-f172.google.com (mail-io0-f172.google.com [209.85.223.172]) (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 D6751113E; Mon, 2 Jan 2017 15:55:45 +0000 (UTC) (envelope-from jonathan.robert.anderson@gmail.com) Received: by mail-io0-f172.google.com with SMTP id d9so414169764ioe.0; Mon, 02 Jan 2017 07:55:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=6Usl41P6UcjnN9X1wtjU38miVgjJs5f6x4DbpYPmJ20=; b=BIJM1e+oSjKwgjoCIhQAOvlT9sCLpRCn5TiWY8bCINxBAdwQWHJRATfDydHXfCmx/1 /QUI0zDp8wnbk8bPmwEDpbucVsPMpkAKwy57Umrq9wWB4HR+QY+ZK8WXbrb5QNur7J29 7s72Ez4yi/lfphSCtxYOJRXVePfLtMquuS1BIce2DZDpKUIHwpRHZuJQp3ECZ1LywSnH piQaPBIPV0kxGoaB03559MYRbeMhoP1A8P+CDKqmB66GLWWfZ73jKaXOwuMqe79a2NBn IcOw2jCHxi76SHc30R9P+bF1jYmIF5gbJD3EhfS4vt0dgLnqwVU5vQnNFj0mQd8/mwO0 rrsg== X-Gm-Message-State: AIkVDXL4NYzDSq0sNR6r2vqvxxX4thOFKpLsVWX6I77EJWetBJVt3mif1S8tfTJ/5z9vMg== X-Received: by 10.107.14.8 with SMTP id 8mr38627728ioo.11.1483365732234; Mon, 02 Jan 2017 06:02:12 -0800 (PST) Received: from mail-it0-f45.google.com (mail-it0-f45.google.com. [209.85.214.45]) by smtp.gmail.com with ESMTPSA id l73sm32067201ioe.1.2017.01.02.06.02.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Jan 2017 06:02:11 -0800 (PST) Received: by mail-it0-f45.google.com with SMTP id 75so248275832ite.1; Mon, 02 Jan 2017 06:02:11 -0800 (PST) X-Received: by 10.36.64.21 with SMTP id n21mr45019277ita.27.1483365730971; Mon, 02 Jan 2017 06:02:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.165.78 with HTTP; Mon, 2 Jan 2017 06:01:50 -0800 (PST) From: Jonathan Anderson Date: Mon, 2 Jan 2017 10:31:50 -0330 X-Gmail-Original-Message-ID: Message-ID: Subject: PQ_LAUNDRY: unexpected behaviour To: markj@freebsd.org, alc@freebsd.org Cc: freebsd-current Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 02 Jan 2017 15:55:46 -0000 Hi all, I'm seeing some unexpected PQ_LAUNDRY behaviour on something fairly close to -CURRENT (drm-next-4.7 with an IFC on 26 Dec). Aside from the use of not-quite-CURRENT, it's also very possible that I don't understand how the laundry queue is supposed to work. Nonetheless, I thought I'd check whether there is a tunable I should change, an issue with the laundry queue itself, etc. After running X overnight (i915 can now run overnight on drm-next-4.7!), I end up with a little over half of my system memory in the laundry queue and a bunch of swap utilization. Even after closing X and shutting down lots of services, I see the following in top: ``` Mem: 977M Active, 31M Inact, 4722M Laundry, 1917M Wired, 165M Free ARC: 697M Total, 67M MFU, 278M MRU, 27K Anon, 22M Header, 331M Other Swap: 4096M Total, 2037M Used, 2059M Free, 49% Inuse PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 911 root 1 52 0 57788K 4308K select 1 0:00 0.00% sshd 974 root 1 20 0 43780K 0K wait 2 0:00 0.00% 1406 jon 1 20 0 33520K 2748K select 0 0:04 0.00% gpg-agent 2038 jon 1 20 0 31280K 5452K ttyin 3 0:18 0.00% zsh 1251 jon 1 22 0 31280K 4500K pause 3 0:02 1.46% zsh 7102 jon 1 20 0 31280K 3744K ttyin 0 0:00 0.00% zsh 1898 jon 1 20 0 31280K 3036K ttyin 1 0:00 0.00% zsh 1627 jon 1 21 0 31280K 0K pause 0 0:00 0.00% 22989 jon 1 20 0 31152K 6020K ttyin 1 0:01 0.00% zsh 22495 jon 1 49 0 31152K 6016K ttyin 0 0:02 0.00% zsh 1621 jon 1 20 0 28196K 8816K select 2 0:40 0.00% tmux 6214 jon 1 52 0 27008K 2872K ttyin 1 0:00 0.00% zsh 6969 jon 1 52 0 27008K 2872K ttyin 3 0:00 0.00% zsh 6609 root 1 20 0 20688K 4604K select 1 0:00 0.00% wpa_supplicant 914 root 1 20 0 20664K 5232K select 2 0:02 0.00% sendmail 917 smmsp 1 20 0 20664K 0K pause 0 0:00 0.00% 24206 jon 1 23 0 20168K 3500K CPU0 0 0:00 0.00% top 921 root 1 20 0 12616K 608K nanslp 1 0:00 0.00% cron ``` Are there any things I could do (e.g., sysctls, tunables) to figure out what's happening? Can I manually force the laundry to be done? `swapoff -a` fails due to a lack of memory. Thanks, Jon -- jonathan@FreeBSD.org