From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'David Woodhouse'" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: RE: [PATCH] Obsolete nodes that are unlinked when possible
Date: Sat, 21 Apr 2007 10:56:49 +0200 [thread overview]
Message-ID: <00fe01c783f2$ff8810a0$020120ac@Jocke> (raw)
In-Reply-To: <1177103631.30621.35.camel@shinybook.infradead.org>
> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: den 20 april 2007 23:14
> To: Joakim Tjernlund
> Cc: linux-mtd@lists.infradead.org
> Subject: RE: [PATCH] Obsolete nodes that are unlinked when possible
>
> On Thu, 2007-04-19 at 21:34 +0200, Joakim Tjernlund wrote:
> > Ping.
>
> Sorry for taking so long to look at this. Did you test this without
> SUMMARY support?
hmm, not sure. I think so, but not much. The idea was that to get
some testing, you need to enable its use in MTD git.
>
> I agree that we ought to make the summary code _not_ imply
> !jffs2_can_mark_obsolete(). There's a few things I want to
> change about
> the summary code -- the nodes are currently about twice as
> large as they
> need to be, too. I'll look at that soon.
Rigth, but more important is that the GC procedure needs to GC
more aggressively, otherwise you will end up with a very fragmented
FS in some cases.
ATM I am doing board bringup and won't be able to spend any time
on JFFS2.
Jocke
prev parent reply other threads:[~2007-04-21 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 15:45 [PATCH] Obsolete nodes that are unlinked when possible Joakim Tjernlund
2007-03-16 16:14 ` Joakim Tjernlund
2007-03-16 16:27 ` Artem Bityutskiy
2007-03-16 17:04 ` Joakim Tjernlund
2007-03-16 17:26 ` Artem Bityutskiy
2007-03-19 10:55 ` Ferenc Havasi
2007-03-19 14:56 ` Joakim Tjernlund
2007-04-19 19:34 ` Joakim Tjernlund
2007-04-20 21:13 ` David Woodhouse
2007-04-21 8:56 ` Joakim Tjernlund [this message]
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='00fe01c783f2$ff8810a0$020120ac@Jocke' \
--to=joakim.tjernlund@transmode.se \
--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