| 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
| ||
|
Date: Tue, 06 Mar 2012 13:42:12 -0500 From: "Martin K. Petersen" <martin.petersen@...cle.com> To: Eric Sandeen <sandeen@...hat.com> Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org, Lukas Czerner <lczerner@...hat.com> Subject: Re: Some interesting input from a flash manufacturer >>>>> "Eric" == Eric Sandeen <sandeen@...hat.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 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists