From: Bernhard Priewasser <priewasser@gmail.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: "Artem B. Bityuckiy" <dedekind@yandex.ru>, linux-mtd@lists.infradead.org
Subject: Re: Testing JFFS2 using mtdram
Date: Tue, 23 Aug 2005 16:47:34 +0200 [thread overview]
Message-ID: <430B3706.7080208@gmail.com> (raw)
In-Reply-To: <20050822094433.GA10958@wohnheim.fh-wedel.de>
> I did that for ramtd. Allocate an array of pointers and then lazily
> allocate memory for those pointers.
Did anyone do something similar for mtdram too?
I tried it quick & dirty, but didn't work :-) If there's a solution for
mtdram I would be grateful, otherwise I had to try further.
mtdram's/vmalloc()'s total size limit indeed is rather low for extensive
testing.
Regards,
Bernhard
next prev parent reply other threads:[~2005-08-23 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 7:43 Testing JFFS2 using mtdram Bernhard Priewasser
2005-08-22 8:47 ` Ferenc Havasi
2005-08-22 8:58 ` Artem B. Bityuckiy
2005-08-22 9:44 ` Jörn Engel
2005-08-23 14:47 ` Bernhard Priewasser [this message]
2005-08-23 14:57 ` Jörn Engel
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=430B3706.7080208@gmail.com \
--to=priewasser@gmail.com \
--cc=dedekind@yandex.ru \
--cc=joern@wohnheim.fh-wedel.de \
--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.