public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Duplication of dirent names in JFFS2 summary
Date: Fri, 19 May 2006 15:32:56 +0400	[thread overview]
Message-ID: <446DACE8.1000809@yandex.ru> (raw)
In-Reply-To: <1147999465.13399.33.camel@shinybook.infradead.org>

David Woodhouse wrote:
> It's a little unfortunate that we have to actually keep a second copy of
> the name in the summary. Is there any way we could avoid it?
> 
> One possibility might be to refrain from storing the name in the dirent
> node itself -- store it _only_ in the summary. This could happen only
> during garbage collection -- when we GC a dirent node, we could write it
> out _without_ its name. In fact, we could possibly refrain from writing
> the GC'd dirent to the log at all -- put it _only_ in the summary.
> 
> That does break backwards compatibility though, which isn't ideal.
And it's just bad:

o it's hacky;
o it'll introduce many if()s in code and make it even more copmplecated;
o finally, it'll interfer robustness: if the summary node get's 
corrupted, we may loose a lot - not just one node;

I believe that this approach has to be vetoed.

> Another possibility might be to omit the full name from the summary, but
> to store only the hash (or name_crc) instead. We hardly ever actually
> need the full name -- it's only used if there's a hash collision, in
> jffs2_add_fd_to_list().
Good idea.

-- 
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.

  parent reply	other threads:[~2006-05-19 11:33 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 [this message]
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

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=446DACE8.1000809@yandex.ru \
    --to=dedekind@yandex.ru \
    --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