From: David Brownell <david-b@pacbell.net>
To: Pierre Ossman <pierre@ossman.eu>
Cc: "Wolfgang Mües" <wolfgang.mues@auerswald.de>,
"Matt Fleming" <matt@console-pimps.org>,
"Pierre Ossman" <drzeus@drzeus.cx>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mike Frysinger" <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc_spi: use EILSEQ for possible transmission errors
Date: Wed, 20 May 2009 19:02:51 -0700 [thread overview]
Message-ID: <200905201902.51377.david-b@pacbell.net> (raw)
In-Reply-To: <20090520120851.49783a8e@mjolnir.ossman.eu>
On Wednesday 20 May 2009, Pierre Ossman wrote:
> > Remember that the
> > firmware in the card can leverage "that's erased" knowledge for
> > things like wear leveling. SSDs and other storage devices would
> > likewise benefit from such knowledge. I'm quite certain there's
> > been discussion about adding support for that in the block layer.
>
> It's already in AFAIK. I even had code for hooking it up to mmc_block.
> But it didn't produce any measurable results so I never merged it.
I'd expect the results would take time to show. As in, they would
facilitate wear leveling logic, which may be difficult to measure
except by testing various cards to destruction ... even for vendors
that *do* have decent wear leveling. :)
next prev parent reply other threads:[~2009-05-21 2:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 11:24 [PATCH] mmc_spi: use EILSEQ for possible transmission errors Wolfgang Mües
2009-05-19 11:29 ` Matt Fleming
2009-05-19 11:47 ` Wolfgang Mües
2009-05-20 7:53 ` Matt Fleming
2009-05-20 4:49 ` David Brownell
2009-05-20 8:35 ` Wolfgang Mües
2009-05-20 9:20 ` David Brownell
2009-05-20 10:08 ` Pierre Ossman
2009-05-21 2:02 ` David Brownell [this message]
2009-05-25 9:04 ` Wolfgang Mües
2009-05-25 9:43 ` David Brownell
2009-05-25 10:18 ` Wolfgang Mües
2009-05-25 11:50 ` Pierre Ossman
2009-05-25 14:59 ` Wolfgang Mües
2009-06-09 18:07 ` Pierre Ossman
2009-06-10 7:29 ` Wolfgang Mües
2009-06-10 7:37 ` Matt Fleming
2009-06-13 10:57 ` Pierre Ossman
2009-05-25 11:48 ` Pierre Ossman
2009-05-20 10:31 ` Wolfgang Mües
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=200905201902.51377.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=pierre@ossman.eu \
--cc=vapier.adi@gmail.com \
--cc=wolfgang.mues@auerswald.de \
/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