Date: Wed, 13 Mar 2002 16:27:41 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Dag-Erling Smorgrav <des@ofug.org> Cc: arch@FreeBSD.ORG Subject: Re: dumpsys() rewrite Message-ID: <15503.50253.527438.195997@grasshopper.cs.duke.edu> In-Reply-To: <xzpbsds8o8n.fsf@flood.ping.uio.no> References: <xzp3cz5v7rp.fsf@flood.ping.uio.no> <20020313093805.GA29679@genius.tao.org.uk> <xzp7kogbwmy.fsf@flood.ping.uio.no> <p05101560b8b522a7f8a1@[128.113.24.47]> <xzpbsds8o8n.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav writes: > Garance A Drosihn <drosih@rpi.edu> writes: > > Would it make any sense to compress it in the 'gzip' sense of > > the word (or some simpler algorithm)? > > Not really. The compression rate is not sufficiently predictable, and > dumping would be s...l...o...w... > You might not want to discount it out of hand. Other OSes (at least Tru64, possibly others) do compressed dumps effectively. Investigating this, once you've gotten a unified dumpsys, is a potential Junior Kernel Hacker task. Your dumpsys cleanup & proposed format with a nice little header at the front will facilitate work like this, as well as partial dumps, (which I'm partial to ;) to be easily integrated. Drew 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?15503.50253.527438.195997>