From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Flash erase groups and filesystems
Date: Tue, 16 Aug 2005 19:09:12 +0200 [thread overview]
Message-ID: <43021DB8.70909@drzeus.cx> (raw)
In-Reply-To: <20050816162735.GB21462@wohnheim.fh-wedel.de>
Jörn Engel wrote:
>Question came up before, albeit with a different phrasing. One
>possible approach to benefit from this ability would be to create a
>"forget" operation. When a filesystem already knows that some data is
>unneeded (after a truncate or erase operation), it will ask the device
>to forget previously occupied blocks.
>
>The device then has the _option_ of handling the forget operation.
>Further reads on these blocks may return random data.
>
>And since noone stepped up to implement this yet, you can still get
>all the fame and glory yourself! ;)
>
>
I'm not sure we're talking about the same thing. I'm not suggesting new
features in the VFS layer. I want to know if something breaks if I
implement this erase feature in the MMC layer. In essence the file
system has marked the sectors as "forget" by issuing a write to them.
The question is if it is assumed that they are unchanged if the write
fails half-way through.
I'd have to say that this is a dangerous assumption to make already
today since some systems might not be able to tell where it fails if a
large chunk of data is given to it, perhaps because of a deep pipeline
before it actually reaches the physical storage.
Rgds
Pierre
next prev parent reply other threads:[~2005-08-16 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 20:21 Flash erase groups and filesystems Pierre Ossman
2005-08-16 16:27 ` Jörn Engel
2005-08-16 17:09 ` Pierre Ossman [this message]
2005-08-16 18:13 ` Jörn Engel
2005-08-16 18:52 ` Jörn Engel
2005-08-17 11:35 ` Pierre Ossman
2005-08-17 11:45 ` Jörn Engel
2005-08-17 14:35 ` Pavel Machek
2005-08-18 11:09 ` linux-os (Dick Johnson)
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=43021DB8.70909@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=joern@wohnheim.fh-wedel.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.