| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200905201902.51377.david-b@pacbell.net> Date: Wed, 20 May 2009 19:02:51 -0700 From: David Brownell <david-b@...bell.net> To: Pierre Ossman <pierre@...man.eu> Cc: Wolfgang Mües <wolfgang.mues@...rswald.de>, "Matt Fleming" <matt@...sole-pimps.org>, "Pierre Ossman" <drzeus@...eus.cx>, "Andrew Morton" <akpm@...ux-foundation.org>, "Mike Frysinger" <vapier.adi@...il.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] mmc_spi: use EILSEQ for possible transmission errors 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. :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists