All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: 小明 <kevin@gv.com.tw>
Cc: linux-mtd@lists.infradead.org
Subject: Re: No free space left for GC
Date: Tue, 20 Aug 2002 09:59:30 +0200	[thread overview]
Message-ID: <1029830371.22775.150.camel@thomas.tec.linutronix.de> (raw)
In-Reply-To: <015501c247f3$d13176a0$b30210ac@gv.com.tw>

On Tue, 2002-08-20 at 04:46, 小明 wrote:
> in our own old nand flash system
> we always keep 1 nand-flash-block for garbage collection in block device
> driver
> (8k/8MB,16k/64MB)
> it never endless gc, but when diskfull,the speed is really slow
> finally we reserved more space(512k) for gc to  make gc faster
> those reversed space is not showed in fs layer
> we report (real size-reserved space) to fs layer
> and we use minix as fs layer
> (we do  bad block management, wear leveling, error correction,
> all in block device driver not in fs layer)
> recently, we need compression , so we try jffs2:)
> i think the design of jffs2 is also better than our old one:)
1. Please keep answers to mailinglist posting on the list. Thanks.

2. The endless gc, which used up all blocks, is fixed now. I will do
some more tests and put a final version into CVS today.

-- 
Thomas 
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  parent reply	other threads:[~2002-08-20  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-17 22:35 No free space left for GC Thomas Gleixner
2002-08-19  9:37 ` Massive file corruption Joakim Tjernlund
2002-08-19 21:47 ` No free space left for GC Thomas Gleixner
2002-08-19 22:34   ` Thomas Gleixner
2002-08-20 10:03     ` David Woodhouse
     [not found]   ` <015501c247f3$d13176a0$b30210ac@gv.com.tw>
2002-08-20  7:59     ` Thomas Gleixner [this message]
2002-08-20 15:47       ` Thomas Gleixner
2002-08-21  6:44         ` can i use the cvs code directly in kernel 2.2.19 ? 小明
2002-08-21  7:56           ` Thomas Gleixner

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=1029830371.22775.150.camel@thomas.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=kevin@gv.com.tw \
    --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.