From: David Woodhouse <dwmw2@infradead.org>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: Duplication of dirent names in JFFS2 summary
Date: Fri, 19 May 2006 16:37:56 +0100 [thread overview]
Message-ID: <1148053076.3875.186.camel@pmac.infradead.org> (raw)
In-Reply-To: <1148051254.3199.54.camel@sauron.oktetlabs.ru>
On Fri, 2006-05-19 at 19:07 +0400, Artem B. Bityutskiy wrote:
> > First, there's the case where we've garbage-collected a dirent node but
> > haven't _yet_ deleted the original. But deleting the original is the
> > whole _point_ in GC, so that's not a common case.
> Sorry, -ENOPARSE on "But deleting the original is the whole _point_ in
> GC, so that's not a common case."
Q: Why do we write new nodes out during GC?
A: So that we can delete the original.
Q: What is the point in GC?
A: The point in GC is that we can delete the original nodes.
Better now?
My point is that when we've written out a colliding node during garbage
collection, that is because we intend to delete the original node real
soon now -- that deletion is what the GC is _for_. That's the whole
_point_ in the GC.
So we needn't worry too much about these collisions -- they'll be
short-lived and hence uncommon.
--
dwmw2
prev parent reply other threads:[~2006-05-19 15:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 0:44 Duplication of dirent names in JFFS2 summary David Woodhouse
2006-05-19 1:01 ` David Woodhouse
2006-05-19 11:53 ` David Woodhouse
2006-05-19 11:58 ` Artem B. Bityutskiy
2006-05-19 12:11 ` David Woodhouse
2006-05-19 12:14 ` Artem B. Bityutskiy
2006-05-19 12:31 ` David Woodhouse
2006-05-19 14:34 ` Artem B. Bityutskiy
2006-05-19 14:59 ` David Woodhouse
2006-05-19 16:41 ` David Woodhouse
2006-05-19 16:43 ` David Woodhouse
2006-05-19 6:05 ` Jörn Engel
2006-05-19 10:08 ` David Woodhouse
2006-05-19 11:32 ` Artem B. Bityutskiy
2006-05-19 11:57 ` Artem B. Bityutskiy
2006-05-19 12:05 ` Artem B. Bityutskiy
2006-05-19 12:23 ` David Woodhouse
2006-05-19 14:17 ` Artem B. Bityutskiy
2006-05-19 14:50 ` David Woodhouse
2006-05-19 15:07 ` Artem B. Bityutskiy
2006-05-19 15:26 ` Artem B. Bityutskiy
2006-05-19 15:33 ` David Woodhouse
2006-05-19 15:38 ` Artem B. Bityutskiy
2006-05-19 15:43 ` David Woodhouse
2006-05-19 15:46 ` Artem B. Bityutskiy
2006-05-20 8:38 ` Artem B. Bityutskiy
2006-05-20 9:08 ` Artem B. Bityutskiy
2006-05-19 15:37 ` David Woodhouse [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=1148053076.3875.186.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=dedekind@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