From owner-freebsd-hackers Fri Feb 19 6:13:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penrose.isocor.ie (penrose.isocor.ie [194.106.155.117]) by hub.freebsd.org (Postfix) with ESMTP id AE47E116AF for ; Fri, 19 Feb 1999 06:13:50 -0800 (PST) (envelope-from peter.edwards@isocor.ie) Received: from isocor.ie (194.106.155.218) by penrose.isocor.ie; 19 Feb 1999 14:14:16 +0000 Message-ID: <36CD7145.EC9EA9D5@isocor.ie> Date: Fri, 19 Feb 1999 14:12:21 +0000 From: Peter Edwards Organization: ISOCOR X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: savecore before swapon? References: <199902171836.TAA00897@yedi.iaf.nl> <199902180049.QAA13082@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, How about _dumping_ to the end of the swap device, rather than hacking on the swap code. > :But this might be a lot of work, I'm not familiar with the VM. Ditto. Matthew Dillon wrote: > > :Or start allocating swap 'backwards' from the high block# on the disk > :downwards. Assuming swap > physical mem and dumps starting at swap offset 0 > :this should be safe at all times (unless fsck really allocates all swap > :of course ;-) > : > Hmm. Well, I don't want to reverse-index the swap allocation but it > would be possible to set the hinting on the swap radix tree bitmap > to allocate higher swap blocks first. I think it would be a little too > much of a hack to be worthy of the kernel, though. > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message