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:08:39 +0200 [thread overview]
Message-ID: <3EE84317.1090307@imc-berlin.de> (raw)
In-Reply-To: 1055347637.2097.240.camel@passion.cambridge.redhat.com
David Woodhouse schrieb:
> On Wed, 2003-06-11 at 17:03, Steven Scholz wrote:
>
>>Is it safe to just do a
>>
>>~ # kill -s SIGSTOP `pidof jffs2_gcd_mtd0`
>>
>>even if my root fs is on this JFFS2 partition?
>
>
> Yes.
>
>
>>(I just tried it now and it seems to work. But IIRC a while ago my
>>system hung when I did something like that...)
>
>
> It shouldn't. The GC thread remains strictly an optimisation (and
> doesn't exist in the eCos port, etc.)
>
David,
two more questions please.
1.) What happens if I send multiple SIGSTOPs or SIGCONTs to the
thread? Does she handle (i.e. ignore) that properly?
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?
I suppose that a few more sectors will be examened and written...
(10ms, 100ms, 1000ms ...???)
Will it then just continue after a SIGCONT? Or will start all over again?
Thanks!
Steven
next prev parent reply other threads:[~2003-06-12 9:08 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 [this message]
2003-06-12 9:18 ` David Woodhouse
2003-06-12 9:35 ` Steven Scholz
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=3EE84317.1090307@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 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.