X-Spam-Checker-Version: SpamAssassin 3.4.0-r929098 (2010-03-30) on oss.sgi.com X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.4.0-r929098 Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id o74Bqj5f032262 for ; Wed, 4 Aug 2010 06:52:45 -0500 X-ASG-Debug-ID: 1280922784-163e020a0000-NocioJ X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from uplift.swm.pp.se (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 614431E3D32E for ; Wed, 4 Aug 2010 04:53:04 -0700 (PDT) Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by cuda.sgi.com with ESMTP id rKoxrBR5RM9rFA4a for ; Wed, 04 Aug 2010 04:53:04 -0700 (PDT) Received: by uplift.swm.pp.se (Postfix, from userid 501) id 3715E9F; Wed, 4 Aug 2010 13:53:03 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 35E5B9C; Wed, 4 Aug 2010 13:53:03 +0200 (CEST) Date: Wed, 4 Aug 2010 13:53:03 +0200 (CEST) From: Mikael Abrahamsson To: Christoph Hellwig cc: Dominik Brodowski , Michael Monnerie , linux-raid@vger.kernel.org, xfs@oss.sgi.com, linux-kernel@vger.kernel.org, dm-devel@redhat.com X-ASG-Orig-Subj: Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs Subject: Re: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs In-Reply-To: <20100804111803.GA32643@infradead.org> Message-ID: References: <20100804073546.GA7494@comet.dominikbrodowski.net> <20100804085039.GA11671@infradead.org> <20100804091317.GA27779@isilmar-3.linta.de> <20100804092122.GA2998@infradead.org> <20100804073546.GA7494@comet.dominikbrodowski.net> <201008041116.09822@zmi.at> <20100804102526.GB13766@isilmar-3.linta.de> <20100804111803.GA32643@infradead.org> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) Organization: People's Front Against WWW MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Barracuda-Connect: swm.pp.se[212.247.200.143] X-Barracuda-Start-Time: 1280922785 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.37004 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on oss.sgi.com X-Virus-Status: Clean On Wed, 4 Aug 2010, Christoph Hellwig wrote: > The good news is that you have it tracked down, the bad news is that I > know very little about dm-crypt. Maybe the issue is the single threaded > decryption in dm-crypt? Can you check how much CPU time the dm crypt > kernel thread uses? I'm not sure it's that. I have a Core i5 with AES-NI and that didn't significantly increase my overall performance, as it's not there the bottleneck is (at least in my system). I earlier sent out an email wondering if someone could shed some light on how scheduling, block caching and read-ahead works together when one does disks->md->crypto->lvm->fs, becase that's a lot of layers and potentially a lot of unneeded buffering, readahead and scheduling magic? -- Mikael Abrahamsson email: swmike@swm.pp.se