On Thu, Jun 12 2014 at 10:13am -0400, Mike Snitzer <snitzer@xxxxxxxxxx> wrote: > Hi Linus, > > This pull request is later than I'd have liked because I was waiting for > some performance data to help finally justify sending the long-standing > dm-crypt cpu scalability improvements upstream. Unfortunately we came > up short, so those dm-crypt changes will continue to wait, but it seems > we're not far off. I'm sharing this because I recently saw you use dm-crypt with Fedora on your workstation. Just wanted to let you know that these same dm-crypt changes are staged in for-next (like they were for months). But now with the added ability to use feature flags to disable the new changes that proved to hurt some workloads. If curious, feel free to see the topmost 7 commits here: https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-for-3.20 Those who are cc'd are involved with validating these dm-crypt changes against the new 3.20 baseline. If all goes as expected I'll have another 3.20 merge pull request for you by the end of the week (with context for where impressive performance improvements have been seen). Mike -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
