public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Flash erase groups and filesystems
Date: Wed, 17 Aug 2005 16:35:35 +0200	[thread overview]
Message-ID: <20050817143534.GC516@openzaurus.ucw.cz> (raw)
In-Reply-To: <43021DB8.70909@drzeus.cx>

Hi!

> >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.

Journaling filesystems may not like finding 0xff's all over their journal...
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         


  parent reply	other threads:[~2005-08-18 10:47 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
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 [this message]
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=20050817143534.GC516@openzaurus.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox