From: Pavel Machek <pavel@suse.cz>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org, Frank Ronny Larsen <frankrl@nhn.no>,
Frank Ronny Larsen <gobo@gimle.nu>,
Jannik Rasmussen <jannik@east.no>,
Lars Christian Nygård <lars@snart.com>
Subject: Re: ext2 compression: How about using the Netware principle?
Date: Wed, 22 Nov 2000 13:29:23 +0000 [thread overview]
Message-ID: <20001122132922.A41@toy> (raw)
In-Reply-To: <3A193A12.9B384B61@karlsbakk.net>
In-Reply-To: <3A193A12.9B384B61@karlsbakk.net>; from roy@karlsbakk.net on Mon, Nov 20, 2000 at 03:49:55PM +0100
Hi!
> - A file is saved to disk
> - If the file isn't touched (read or written to) within <n> days
> (default 14), the file is compressed.
> - If the file isn't compressed more than <n> percent (default 20), the
> file is flagged "can't compress".
> - All file compression is done on low traffic times (default between
> 00:00 and 06:00 hours)
> - The first time a file is read or written to within the <n> days
> interval mentioned above, the file is addressed using realtime
> compression. The second time, the file is decompressed and commited to
> disk (uncompressed).
Oops, that means that merely reading a file followed by powerfail can
lead to you loosing the file. Oops.
Besides: you can do this in userspace with existing e2compr. Should take
less than 2 days to implement.
> Results:
> A minimum of CPU time is wasted compressing/decompressing files.
> The average server I've been out working with have an effective
> compression of somewhere between 30 and 100 per cent.
Results: NOP at machines that are never on in that time, random corruption
after powerfail between 0:00-6:00, .. Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 14:49 ext2 compression: How about using the Netware principle? Roy Sigurd Karlsbakk
2000-11-21 20:00 ` Jorge Nerin
2000-11-22 13:29 ` Pavel Machek [this message]
2000-11-23 11:07 ` Anders K. Pedersen
2000-11-23 12:51 ` Roy Sigurd Karlsbakk
2000-11-24 10:15 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001122132922.A41@toy \
--to=pavel@suse.cz \
--cc=frankrl@nhn.no \
--cc=gobo@gimle.nu \
--cc=jannik@east.no \
--cc=lars@snart.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox