From: David Woodhouse <dwmw2@infradead.org>
To: joakim.tjernlund@lumentis.se
Cc: linux-mtd@lists.infradead.org
Subject: Re: Question/suggestion
Date: Tue, 16 Oct 2001 17:37:59 +0100 [thread overview]
Message-ID: <28153.1003250279@redhat.com> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLEEJHEPAA.joakim.tjernlund@lumentis.se>
joakim.tjernlund@lumentis.se said:
> I have noticed that when I mount a jffs2 FS(created with mkfs.jffs2)
> for the first time and look at the output of the df command, I see
> that "Use%" field slowly rise to 100% and then it drops back to ~15%
> and then it stays there. During this rise I also noticed that kupdate
> was eating alot of CPU(~80%)
> Is this normal?
The first time it's mounted, all the blocks need to be erased and
formatted correctly. That's done in the context of kupdated. The Use% field
is high because the blocks are being taken out of the list of available
blocks - we should probably fix that.
> Is there any point to have a config option for preferred compression
> algorithm order?
Probably not. If you want rtime first you might as well just omit zlib
completely. And yes, rtime will be faster.
--
dwmw2
next prev parent reply other threads:[~2001-10-16 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 14:05 Read Only FS Jose Rodríguez Argente
2001-10-16 1:36 ` Tim Riker
2001-10-16 5:26 ` David Woodhouse
2001-10-16 16:29 ` Question/suggestion Joakim Tjernlund
2001-10-16 16:37 ` David Woodhouse [this message]
2001-10-17 6:43 ` Question/suggestion Joakim Tjernlund
2001-10-17 8:00 ` Question/suggestion David Woodhouse
2001-10-18 10:00 ` Question/suggestion Joakim Tjernlund
2001-10-18 10:09 ` Question/suggestion David Woodhouse
2001-10-18 10:27 ` Question/suggestion Joakim Tjernlund
2001-10-18 10:38 ` Question/suggestion David Woodhouse
2001-10-18 14:15 ` Question/suggestion Joakim Tjernlund
2001-10-18 14:16 ` Question/suggestion David Woodhouse
2001-11-02 11:37 ` Question/suggestion Joakim Tjernlund
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=28153.1003250279@redhat.com \
--to=dwmw2@infradead.org \
--cc=joakim.tjernlund@lumentis.se \
--cc=linux-mtd@lists.infradead.org \
/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.