Date: Wed, 13 Mar 2002 10:42:41 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Dag-Erling Smorgrav <des@ofug.org>, Josef Karthauser <joe@tao.org.uk> Cc: arch@FreeBSD.ORG, peter@FreeBSD.ORG, jake@FreeBSD.ORG Subject: Re: dumpsys() rewrite Message-ID: <p05101560b8b522a7f8a1@[128.113.24.47]> In-Reply-To: <xzp7kogbwmy.fsf@flood.ping.uio.no> References: <xzp3cz5v7rp.fsf@flood.ping.uio.no> <20020313093805.GA29679@genius.tao.org.uk> <xzp7kogbwmy.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:16 AM +0100 3/13/02, Dag-Erling Smorgrav wrote: >Josef Karthauser <joe@tao.org.uk> writes: > > It would be fantastic to be able to compress the memory image > > as it is dumped to disk. That would speed it up a bit in most > > cases. If each dump_write reads memory directly rather than > > going through a common function this is never going to be easy > > to do. > >dumpsys() controls what is written and when. It is perfectly >conceivable for dumpsys() to do the same kind of hole compression >that savecore(1) does, but it would be *much* slower and ... Would it make any sense to compress it in the 'gzip' sense of the word (or some simpler algorithm)? Or does it already do some of that? -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101560b8b522a7f8a1>