From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, Lukas Czerner <lczerner@redhat.com>
Subject: Re: Some interesting input from a flash manufacturer
Date: Tue, 06 Mar 2012 13:42:12 -0500 [thread overview]
Message-ID: <yq1r4x5k1vf.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <4F5135F0.6090100@redhat.com> (Eric Sandeen's message of "Fri, 02 Mar 2012 15:04:48 -0600")
>>>>> "Eric" == Eric Sandeen <sandeen@redhat.com> writes:
>> We also talked about ways that we might right some application notes
>> so that handset OEM's understood how to use mke2fs parameters to
>> optimize their file systems for different types of flash systems, and
>> perhaps ways that the eMMC spec could be enhanced so that key
>> parameters such as erase block size, flash page size, and translation
>> table granularity could be passed back to the block layer, and made
>> available to file system and mkfs.
Eric> Now that would be nice. Could some of this just be piggybacked on
Eric> the existing preferred_io_size-type geometry interfaces?
So far the barrier has been that the flash manufacturers did not want to
disclose the erase block size, etc. That's why the original
standardization efforts in that department were shelved.
If the devices actually start exporting this information I'll be happy
to put it in the topology.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2012-03-06 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 21:00 Some interesting input from a flash manufacturer Theodore Ts'o
2012-03-02 21:04 ` Eric Sandeen
2012-03-02 23:11 ` Ted Ts'o
2012-03-06 1:12 ` Greg Freemyer
2012-03-06 18:44 ` Martin K. Petersen
2012-03-07 0:52 ` Ted Ts'o
2012-03-08 4:36 ` Martin K. Petersen
2012-03-06 18:42 ` Martin K. Petersen [this message]
2012-03-05 7:00 ` Lukas Czerner
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=yq1r4x5k1vf.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).