public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Sun Devil <sundevil007@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: FTLs for NANDSim
Date: Mon, 22 Oct 2007 10:33:08 +0100	[thread overview]
Message-ID: <1193045588.2672.15.camel@shinybook.infradead.org> (raw)
In-Reply-To: <7ee965bc0710200922n2159c5dav4357d1cdce5521e8@mail.gmail.com>

On Sat, 2007-10-20 at 09:22 -0700, Sun Devil wrote:
> 1. Can we write an user level FTL and interface with NANDSim, so that,
> for the application, simulated flash appears to be a physical device,
> and I can format the same volume in what ever way possible?

Yes, I suppose you could. You could access the 'flash' through
the /dev/mtd0 character device, then provide a block device to the
kernel by using something like nbd. It's probably better to do it in the
kernel though.

> 2. Do you have any implementations of FTL at Kernel level?

Yes. We have the simplistic 'mtdblock' which doesn't really do any
translation at all, we have 'FTL' which works only on NOR flash, and we
have 'NFTL' and 'INFTL' for use on DiskOnChip devices. There is a helper
layer which is designed to make it relatively easy for you to provide
your own translation layer, without having to get too deeply involved in
how Linux block device drivers work.

> 3. Are there any NAND Flash simulators that you know of apart from NANDSim?

Well, there's a OneNAND sim too. And it's not that hard to use real NAND
flash either -- see Jörn's new 'Alauda' driver for certain USB devices.

-- 
dwmw2

  reply	other threads:[~2007-10-22  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20 16:22 FTLs for NANDSim Sun Devil
2007-10-22  9:33 ` David Woodhouse [this message]
2007-10-22 16:00   ` Jörn Engel
2007-10-22 16:12     ` Josh Boyer

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=1193045588.2672.15.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sundevil007@gmail.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