public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Estelle HAMMACHE <estelle.hammache@st.com>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd/fs/jffs2 nodemgmt.c,1.115,1.116
Date: Tue, 25 Jan 2005 11:13:53 +0100	[thread overview]
Message-ID: <41F61BE1.10A2DDA8@st.com> (raw)
In-Reply-To: 1106603928.5081.50.camel@tglx.tec.linutronix.de

Thomas Gleixner wrote:
> 
> > - avoid filing blocks on the clean list when they have wasted
> > space
> 
> That's plain wrong.
> 
> Wasted space was introduced to prevent endless garbage collection.
> Wasted space is unreclaimable, because it is less than the minimum node
> size. It's totally correct to file those blocks on the clean list,
> because GC _cannot_ reclaim the wasted space.

Well without this patch I got blocks on the clean list with huge
wasted space, more than the ISDIRTY calculation, when a write that
fills exactly the space left in nextblock also obsoletes nodes
in nextblock (not sure about the exact case it was some time ago).
In jffs2_mark_node_obsolete, if the node belongs to nextblock, the
space is always added to wasted_space - not dirty_space. So I don't
understand whether wasted_space is not what you claim, or it is
not well implemented.

I'm afraid my comment in the log was quite misleading: 
this patch merely prevents filing the block to the clean
list in jffs2_add_physical_node_ref. As the comment in that
function says, the block will be filed to the correct list later 
and with proper ISDIRTY check (or am I missing something ?).

Lastly, I did submit this patch beforehand to the list, even if it was
in a thread on NAND failure. I would have expected you to have
an interest in that thread anyway.

(please excuse me if I sound grumpy. Your comments are a bit
of a cold shower on my newbie enthusiasm. If the patch is really
a problem I will reverse it tonight.)

Estelle

  parent reply	other threads:[~2005-01-25 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24 21:58 mtd/fs/jffs2 nodemgmt.c,1.115,1.116 Thomas Gleixner
2005-01-24 22:09 ` David Woodhouse
2005-01-25 11:17   ` Estelle HAMMACHE
2005-01-26  9:31     ` Estelle HAMMACHE
2005-01-25 10:13 ` Estelle HAMMACHE [this message]
2005-01-25 10:58   ` Thomas Gleixner
2005-01-25 11:55     ` 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=41F61BE1.10A2DDA8@st.com \
    --to=estelle.hammache@st.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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