linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 sumtool bug ?
Date: Wed, 23 May 2007 06:55:11 -0400	[thread overview]
Message-ID: <1179917711.10095.58.camel@shinybook.infradead.org> (raw)
In-Reply-To: <4653F6DE.1090105@parrot.com>

On Wed, 2007-05-23 at 10:10 +0200, Matthieu CASTET wrote:
> PS : about summary, could the sumtool change the order of the nodes to 
> avoid to waste too much space. For example if the eraseblock is 16KB and 
> we have 4 nodes of 4KB. Sumtool will put in the first eraseblock 3 
> nodes, 4KB will be wasted for the sumary node. In this wasted 4KB, we 
> could have put smaller nodes.

Theoretically, yes. But there's easier things to do first. We could
halve the size of the summary node itself, for example.

-- 
dwmw2

      reply	other threads:[~2007-05-23 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  8:10 jffs2 sumtool bug ? Matthieu CASTET
2007-05-23 10:55 ` 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=1179917711.10095.58.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matthieu.castet@parrot.com \
    /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;
as well as URLs for NNTP newsgroup(s).