From owner-svn-src-all@FreeBSD.ORG Sat Dec 15 22:33:47 2012 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 36F85843; Sat, 15 Dec 2012 22:33:47 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 0CD6A8FC1A; Sat, 15 Dec 2012 22:33:47 +0000 (UTC) Received: from [10.0.1.102] (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218]) by elvis.mu.org (Postfix) with ESMTPSA id EC49C1A3C1E; Sat, 15 Dec 2012 14:33:39 -0800 (PST) References: <201212110708.qBB78EWx025288@svn.freebsd.org> <201212121046.43706.jhb@freebsd.org> <201212121658.49048.jhb@freebsd.org> <50C90567.8080406@FreeBSD.org> <50C909BD.9090709@mu.org> <50C91B32.4080904@FreeBSD.org> <50C91CD3.7030900@mu.org> <50C9206D.6080502@FreeBSD.org> <50C9271C.70803@mu.org> <20121215210333.GH1411@garage.freebsd.pl> Mime-Version: 1.0 (1.0) In-Reply-To: <20121215210333.GH1411@garage.freebsd.pl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <03D95002-35FE-4880-80FA-3E97944AB988@mu.org> X-Mailer: iPhone Mail (10A523) From: Alfred Perlstein Subject: Re: svn commit: r244112 - head/sys/kern Date: Sat, 15 Dec 2012 14:33:37 -0800 To: Pawel Jakub Dawidek Cc: Adrian Chadd , "src-committers@FreeBSD.org" , John Baldwin , "svn-src-all@FreeBSD.org" , Alfred Perlstein , Andriy Gapon , Navdeep Parhar , "svn-src-head@FreeBSD.org" X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Dec 2012 22:33:47 -0000 Your use case (small swap & large ram) is exactly why I would like to try th= is.=20 Do you object? Sent from my iPhone On Dec 15, 2012, at 1:03 PM, Pawel Jakub Dawidek wrote: > On Wed, Dec 12, 2012 at 04:53:48PM -0800, Alfred Perlstein wrote: >> Like what if I do gzipp'd kernel dumps next? (on my todo list) How many=20= >> people will complain that "gzip is too dangerous in kernel context foo=20= >> foo!!!!" >>=20 >> Not sure, I guess I'll find out? >=20 > Well... :) savecore(8) has an option to compress the dumps. The only use > case for compressing-while-dumping I see is small swap/dump partition. > I'm not against this change, but I would not use it myself. When you are > dumping your kernel is in undefined state, so the less code you execute > in that state the higher chances your dump will succeed. I much prefer > to either compress the dumps with savecore(8) or use ZFS dataset with > compression enabled for /var/crash/. >=20 > --=20 > Pawel Jakub Dawidek http://www.wheelsystems.com > FreeBSD committer http://www.FreeBSD.org > Am I Evil? Yes, I Am! http://tupytaj.pl