linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Steve Iribarne <siribarne@grid-net.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: bud_replay size question
Date: Fri, 03 Dec 2010 18:07:57 +0200	[thread overview]
Message-ID: <1291392477.2365.64.camel@localhost> (raw)
In-Reply-To: <4CF691F0.9010607@grid-net.com>

On Wed, 2010-12-01 at 10:20 -0800, Steve Iribarne wrote:
> What I'm trying to determine is how to figure out how big the replay_bud 
> LEB list can get based on my configuration.  Is there such a thing or am 
> I just dreaming?

Yeah, maximum amount of buds is max_bud_bytes / leb_size rounded up, I
thing. max_bud_bytes is stored in the superblock (see struct
ubifs_sb_node). The smaller it is, the smaller is the UBIFS journal.

You can control max_bud_bytes with the -j option of mkfs.ubifs. Try to
make it smaller.

Frankly, we (UBIFS authors) made this mechanism, but never really played
with journal size and always used the default one. Please, play with
this and report your findings - you can hit bugs if you start making it
too small or too large, but may be not. Dunno. But it has to make UBIFS
keep the journal smaller.

Alternatively, you can try to look at all UBIFS allocations. I will not
be surprized if it allocates some buffers which are not really neaded in
R/O mode, although we did do some work to allocate less resources when
we are in R/O mode. You can experiment in Linux, because it is easier,
and if you find unneeded buffers, fix this, and then port your changes
to u-boot.

HTH.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2010-12-03 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 18:20 bud_replay size question Steve Iribarne
2010-12-03 16:07 ` Artem Bityutskiy [this message]
2010-12-03 16:14   ` Artem Bityutskiy
2010-12-03 18:20     ` Steve Iribarne

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=1291392477.2365.64.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=siribarne@grid-net.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).