From: Artem Bityutskiy <dedekind1@gmail.com>
To: Nicholas <ciliwung36@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI memory usage on large page nand
Date: Fri, 15 Apr 2011 16:17:03 +0300 [thread overview]
Message-ID: <1302873423.3220.45.camel@localhost> (raw)
In-Reply-To: <1302873226.3220.43.camel@localhost>
On Fri, 2011-04-15 at 16:13 +0300, Artem Bityutskiy wrote:
> On Fri, 2011-04-15 at 17:23 +0800, Nicholas wrote:
> > Dear Artem,
> >
> > Thanks for the information. Indeed it has flexibility to be freed or consumed.
> > Due to my case, i need to use maximum memory space while in the
> > meantime i also need to write files into nand via ubi.
> > 8KB page of nand flash will consume 16MB for a single volume on a
> > single UBI MTD.
> >
> > 1. Is there any idea to reduce the memory consumption ?
>
> Yes. The main idea is as I described: both UBI and UBIFS have several
> multiple PEB-size buffers at attach/mount time. I did not count them,
> but I think there may be about 6 of them. All these buffers are
> allocated using vmalloc(), so you can easily fine all of them, because
> 'vmalloc()' is used only for those buffers.
And note, this is all off the top of my head, I might be mistaken
somewhere. If you need this - you need to spend time with the code and
try. I'm all yours helping you by looking at your patches and advising.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-15 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=GsmJOjurETG930t-TW7uXLR1M6yKXWBSk7ebV@mail.gmail.com>
2011-03-31 3:07 ` UBI memory usage on large page nand Nicholas
2011-04-01 15:31 ` Artem Bityutskiy
2011-04-15 9:23 ` Nicholas
2011-04-15 13:13 ` Artem Bityutskiy
2011-04-15 13:17 ` Artem Bityutskiy [this message]
2011-04-15 13:24 ` Artem Bityutskiy
2011-04-17 9:03 ` Nicholas
2011-04-17 9:16 ` Artem Bityutskiy
2011-04-18 8:29 ` Nicholas
2011-04-18 8:39 ` Artem Bityutskiy
2011-04-20 3:19 ` Nicholas
2011-04-20 7:30 ` Artem Bityutskiy
2011-08-17 6:35 ` Nicholas
2011-08-20 5:17 ` Artem Bityutskiy
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=1302873423.3220.45.camel@localhost \
--to=dedekind1@gmail.com \
--cc=ciliwung36@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.