From owner-freebsd-stable@FreeBSD.ORG Sat Apr 5 07:17:16 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDEAB71 for ; Sat, 5 Apr 2014 07:17:16 +0000 (UTC) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8032E9CE for ; Sat, 5 Apr 2014 07:17:16 +0000 (UTC) Received: from fortune.joker.local (180-198-238-43.nagoya1.commufa.jp [180.198.238.43]) (authenticated bits=0) by dec.sakura.ne.jp (8.14.2/8.14.2/[SAKURA-WEB]/20080708) with ESMTP id s356SuFx013076 for ; Sat, 5 Apr 2014 15:28:56 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 5 Apr 2014 15:28:55 +0900 From: Tomoaki AOKI To: freebsd-stable@freebsd.org Subject: Re: What's up with the swapping since 10/stable Message-Id: <20140405152855.1cfcf37c87bdff3306d0cd6c@dec.sakura.ne.jp> In-Reply-To: References: <533DB9B1.3070500@denninger.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.3.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Apr 2014 07:17:16 -0000 Yes, Karl's patch fixed my swap regression, too. ZFS-root notebook with 8GB RAM, stable/10 amd64. No swap usage is observed after applying his patch, feeling (but not measured) no performance penalty. But unfortunately, the patch haven't been merged even to head. So, anyone chasing vanilla head or stable/10 has no fix yet. On Fri, 4 Apr 2014 09:24:52 +0200 Matthias Gamsjager wrote: > This was an old post and after few week Karl came up with an arc patch > which fixed this issue. -- Tomoaki AOKI junchoon@dec.sakura.ne.jp