All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Priewasser <priewasser@gmail.com>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: GC operation
Date: Mon, 07 Nov 2005 13:47:17 +0100	[thread overview]
Message-ID: <436F4CD5.6030909@gmail.com> (raw)
In-Reply-To: <436A3BBD.5040405@yandex.ru>

Hi Artem,

 > Brr, didn't get it.. GC may be ugly if what?
If someone wants to understand how it works in detail :-)

 >> When and how is GC called?
 > From the GC thread and when there is no (or few) free space to write.
 > In the latter case the writing process is blocked and waits until GC
 > has freed some space.
E.g. if it is considered as neccessary either by jffs2_reserve_space()
or jffs2_thread_should_wake().
Something about the blocking topic... If there is almost no free space
and a write command issued, can it be blocked until the whole partition
is GC'd (worst case)?? What a latency time... Are there mechanisms to
avoid/control this? What about the "erase suspend" thing?

 >> Ah, another one: Are blocks on the erase_pending_list erased beside
 >> the GC cycles?
 > They are erased later, yes.
jffs2_erase_pending_blocks(), am I right? When is it called? I can only
find it in jffs2_write_super() with count=0 and jffs2_find_nextblock()
with count=1.

Many thanks,
Bernhard

  reply	other threads:[~2005-11-07 12:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 16:22 GC operation Bernhard Priewasser
2005-11-03 16:33 ` Artem B. Bityutskiy
2005-11-07 12:47   ` Bernhard Priewasser [this message]
2005-11-08 14:31     ` Artem B. Bityutskiy
2005-11-09 13:23       ` Bernhard Priewasser
2005-11-09 13:41         ` Josh Boyer
2005-11-09 14:47         ` Artem B. Bityutskiy
2005-11-09 17:35           ` Bernhard Priewasser

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=436F4CD5.6030909@gmail.com \
    --to=priewasser@gmail.com \
    --cc=dedekind@yandex.ru \
    --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.