| 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: Wed, 04 Aug 2010 14:02:10 -0400 From: "Martin K. Petersen" <martin.petersen@...cle.com> To: Mark Lord <kernel@...savvy.com> Cc: Nigel Cunningham <nigel@...onice.net>, LKML <linux-kernel@...r.kernel.org>, pm list <linux-pm@...ts.linux-foundation.org> Subject: Re: 2.6.35 Regression: Ages spent discarding blocks that weren't used! >>>>> "Mark" == Mark Lord <kernel@...savvy.com> writes: Mark> Looks to me like more and more things are using the block discard Mark> functionality, and as predicted it is slowing things down Mark> enormously. Mark> The problem is that we still only discard tiny bits (a single Mark> range still??) per TRIM command, rather than batching larger Mark> ranges and larger numbers of ranges into single TRIM commands. Mark> That's a very poor implementation, especially when things start Mark> enabling it by default. Eg. the swap code, mke2fs, etc.. I'm working on aggregation. But it's harder than we initially thought... -- Martin K. Petersen Oracle Linux Engineering -- 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