From: Alex Zarochentsev <zam@namesys.com>
To: David Masover <ninja@slaphack.com>
Cc: reiserfs-list@namesys.com
Subject: Re: when will it end?
Date: Wed, 27 Oct 2004 07:34:43 +0400 [thread overview]
Message-ID: <20041027033443.GE25932@backtop.namesys.com> (raw)
In-Reply-To: <417EF280.10003@slaphack.com>
On Tue, Oct 26, 2004 at 07:57:36PM -0500, David Masover wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have 512 megs of RAM and one 200 gig hard drive (effectively 177 gig
> filesystem) that is 86% full. I started the reiser4 repacker two days
> ago, with very minimal system use since then (an hour or two a day of
> playing music and reading email). See below for my df and top.
>
> Thankfully, the kernel seems intelligent enough about memory management
> that once things other than Doom 3 start, they run reasonably smoothly,
> even video (must be that anticipatory IO scheduler).
>
> Three questions: When will it end? How can I kill it if I get sick of
> waiting?
try this:
echo 0 > /sys/fs/riser4/hda5/repacker/start
> Is it conceivable that the repacker could be optimized to run
> faster?
current repacker code state is 'unsupported', it is even removed from the
latest -mm kernels. Namesys plans are to make the repacker proprietary.
--
Alex.
next prev parent reply other threads:[~2004-10-27 3:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 0:57 when will it end? David Masover
2004-10-27 3:34 ` Alex Zarochentsev [this message]
2004-10-27 6:13 ` David Masover
2004-10-27 8:31 ` Spam
2004-10-27 16:59 ` Hans Reiser
2004-10-27 17:06 ` Spam
2004-10-28 2:09 ` David Masover
2004-10-30 16:23 ` Redeeman
2004-11-18 5:07 ` David Masover
2004-11-18 10:18 ` Christian Mayrhuber
2004-11-22 3:16 ` Thomas Graham
2004-10-27 18:52 ` Alex Zarochentsev
2004-10-28 1:49 ` David Masover
2004-10-28 8:29 ` mjt
-- strict thread matches above, loose matches on Subject: below --
2004-11-18 17:15 Andreas Sundstrom
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=20041027033443.GE25932@backtop.namesys.com \
--to=zam@namesys.com \
--cc=ninja@slaphack.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.