From: Thanasis <thanasis@asyr.hopto.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: jffs2 and kernel config for SDHC Memory Cards
Date: Fri, 06 Mar 2009 22:24:25 +0200 [thread overview]
Message-ID: <49B18679.4030504@asyr.hopto.org> (raw)
In-Reply-To: <20090306182425.GB28349@silver.sucs.org>
on 03/06/2009 08:24 PM Sitsofe Wheeler wrote the following:
> On Fri, Mar 06, 2009 at 03:56:01PM +0200, Thanasis wrote:
>> on 03/06/2009 03:39 PM Thanasis wrote the following:
>>> I want to use two of these Transcend’s Class 6 SDHC (SD High-Capacity)
>>> Memory Cards,
>>> http://www.transcendusa.com/Products/ModDetail.asp?ModNo=147&LangNo=0&Func1No=1&Func2No=13
>>> as part of the filesystem in a netbook (Acer A110L), will mount /home on
>>> one, and /tmp and /var on the other.
>
>> Let me rephrase my questions in order to be clearer:
>> Q1: In order to achieve wear leveling should I format them as jffs2?
>
> This probably won't be very effective as you are already past the
> anecdotal size recommended for jffs2 partitions (I've heard rumours that
> it is best suited to filesystems that are less than 64Mbytes and another
> that says less than 1Gbyte). Additionally you are not providing direct
> access to the raw flash (see
> http://linux-mtd.infradead.org/faq/jffs2.html#L_stick_jffs2 ).
> Performance is probably not gong to be very good.
>
>> Q2: In order to achieve wear leveling, any specific options I should
>> enable in kernel (2.6.28) configuration?
>
> You will be wear levelled by the hardware anyway as the hardware only
> provides a block device interface and you don't have access to the raw
> flash.
>
> ccing Dave Woodhouse as he is the JFFS2 creator.
>
OK. I believe I should stick to ext2, right?
Thanks ;-)
next prev parent reply other threads:[~2009-03-06 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 13:39 jffs2 and kernel config for SDHC Memory Cards Thanasis
2009-03-06 13:56 ` Thanasis
2009-03-06 18:24 ` Sitsofe Wheeler
2009-03-06 20:24 ` Thanasis [this message]
2009-03-06 22:57 ` Sitsofe Wheeler
2009-03-07 16:59 ` Thanasis
2009-03-10 11:23 ` Pavel Machek
2009-03-10 22:05 ` Thanasis
2009-03-15 21:18 ` Pavel Machek
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=49B18679.4030504@asyr.hopto.org \
--to=thanasis@asyr.hopto.org \
--cc=linux-kernel@vger.kernel.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