public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: MTD <linux-mtd@lists.infradead.org>
Subject: Re: Stopping the GC thread?
Date: Thu, 12 Jun 2003 11:35:59 +0200	[thread overview]
Message-ID: <3EE8497F.30402@imc-berlin.de> (raw)
In-Reply-To: 1055409538.2097.438.camel@passion.cambridge.redhat.com

David,

>>2.) What happnens when I send a SIGSTOP in the middle of a running GC?
>>Will it stop immediately? Or will it take a while?
> 
> 
> It'll finish copying the node it's _currently_ garbage-collecting, which
> may involve decompressing up to a page of data, recompressing it and
> writing it out elsewhere. It may also need to wait for erases to
> complete.
> 
> Even after it's stopped, if there are erasable blocks on the queue,
> they'll continue to be erased in the background by kupdated. You cannot
> prevent that.

But the impact on system performance done by kupdated is not as 
critical as the one that's done by the GC intself, is it?

> 
>>I suppose that a few more sectors will be examened and written... 
>>(10ms, 100ms, 1000ms ...???)
> 
> 
> 'sector'?  Read http://sources.redhat.com/jffs2/jffs2.pdf 
I meant flash sectors.

Steven

  reply	other threads:[~2003-06-12  9:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 16:03 Stopping the GC thread? Steven Scholz
2003-06-11 16:07 ` David Woodhouse
2003-06-11 16:12   ` Steven Scholz
2003-06-11 16:18     ` David Woodhouse
2003-06-11 16:20       ` Steven Scholz
2003-06-11 16:23         ` David Woodhouse
2003-06-12  9:08   ` Steven Scholz
2003-06-12  9:18     ` David Woodhouse
2003-06-12  9:35       ` Steven Scholz [this message]
2003-06-12  9:41         ` David Woodhouse
2003-06-12  9:52         ` Jörn Engel

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=3EE8497F.30402@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=dwmw2@infradead.org \
    --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