public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2: mount time, SUMMARY and gc.c ?
Date: Mon, 10 Jan 2005 10:02:04 +0100	[thread overview]
Message-ID: <41E2448C.2060003@imc-berlin.de> (raw)
In-Reply-To: <1105129884.25392.19.camel@weaponx.rchland.ibm.com>

Josh Boyer wrote:

>>Well but "in background" means 99.9% of cpu time!
>>And this slows down the start up of important user applications.
> 
> That's odd...  IIRC the thread schedules itself after every call to
> jffs2_garbage_collect_pass.  By how much are the startup of these apps
> delayed?  If it's using 99.9% of the cpu, maybe there is nothing else
> that your system can do at that particular point?

Ok. Maybe I exaggerated a bit. It consumes much time. But it seems to share it 
with my application. Shortly after boot I see something like 70-80% for gc and 
20% for my app. But this changes after a few seconds.

VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 76K

<6 seconds pause>

init started:  BusyBox v1.00 (2005.01.04-08:42+0000) multi-call binary
<1 seconds pause>
Please press Enter to activate this console.

After this gc is still running.

-- 
Steven Scholz

  reply	other threads:[~2005-01-10  9:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 18:36 JFFS2: mount time, SUMMARY and gc.c ? Steven Scholz
2005-01-07 18:44 ` Steven Scholz
2005-01-07 19:05   ` Artem B. Bityuckiy
2005-01-07 19:11     ` Steven Scholz
2005-01-07 19:24       ` Artem B. Bityuckiy
2005-01-07 19:40       ` Artem B. Bityuckiy
2005-01-07 20:53         ` Todd Poynor
2005-01-08 12:43           ` Artem B. Bityuckiy
2005-01-07 20:31       ` Josh Boyer
2005-01-10  9:02         ` Steven Scholz [this message]
2005-01-07 19:01 ` Artem B. Bityuckiy

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=41E2448C.2060003@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox