Linux NILFS development
 help / color / mirror / Atom feed
From: Chris Samuel <chris-Ru3vu9m2XlBAfugRpC6u6w@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: NILFS usage on NAND and NOR flash memory
Date: Fri, 26 Jun 2009 18:01:48 +1000	[thread overview]
Message-ID: <200906261801.48514.chris@csamuel.org> (raw)
In-Reply-To: <585a0ef70906231842p31130fd5h54cd124c6751ec7b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: Text/Plain, Size: 586 bytes --]

On Wed, 24 Jun 2009 11:42:32 am Jesse Campbell wrote:

> ext3 was tried, but there were so many writes that the location of the
> journal on the SD card burned and the card became unusable.

I know that btrfs (another COW filesystem) has an SSD mode (and an SSD mode 
for non-enterprise SSD's for 2.6.31), I wonder if NILFS could pick its brains 
for these devices ?

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

[-- Attachment #2: Type: text/plain, Size: 158 bytes --]

_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users

  parent reply	other threads:[~2009-06-26  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24  1:42 NILFS usage on NAND and NOR flash memory Jesse Campbell
     [not found] ` <585a0ef70906231842p31130fd5h54cd124c6751ec7b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-26  8:01   ` Chris Samuel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-24 14:33 James M Long

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=200906261801.48514.chris@csamuel.org \
    --to=chris-ru3vu9m2xlbafugrpc6u6w@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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