public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Sunghan Suh <sunghan.suh@samsung.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: questions about parallelism in MTD
Date: Mon, 04 Feb 2013 09:14:13 +0200	[thread overview]
Message-ID: <1359962053.13791.9.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <2CEE1A97B58A432486659DE985FE2F7E@sunghansuh>

[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

On Mon, 2013-01-21 at 14:38 +0900, Sunghan Suh wrote:
> Hi,
> 
> I'm a software engineer who is trying to develop a new flash file system.
> 
> I have some questions about MTD.
> 
> 1. Isn't there any approach to make read/write operations to be non-blocking?
>   For example, a file system writes data to MTD and it doesn't want to wait on I/O completion.
>   While writing, it tries to do other things in order to increase performance.
>   How can I use MTD such a case?

This would be cool to have such an interface. It should be modelled
after the Block I/O interface. But it would anyway have a lot more
restrictions than block I/O and would have many specifics.

At the moment, nothing like this exist. I guess it is just too hard to
implement, so no one dared.

> 2. How can I utilize multiple plane & die architectures in MTD?
>   As MLC & TLC used, write latency is getting much larger. 
>   Instead, flash memory supports multiple plane & die to increase parallelism.
>   Is there a MTD driver fully supporting these features?

I guess the only current way to do this is to make the driver expose
logical eraseblocks/pages which are multiple of physical
eraseblocks/pages, then upper layers will do I/O in larger chunks, and
you will make the physical I/O parallel on the driver level. 

-- 
Best Regards,
Artem Bityutskiy

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

      reply	other threads:[~2013-02-04  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21  5:38 questions about parallelism in MTD Sunghan Suh
2013-02-04  7:14 ` Artem Bityutskiy [this message]

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=1359962053.13791.9.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sunghan.suh@samsung.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