From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tansi.org (ns.km10532-04.keymachine.de [87.118.102.195]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 12 Nov 2010 02:21:45 +0100 (CET) Date: Fri, 12 Nov 2010 02:21:44 +0100 From: Arno Wagner Message-ID: <20101112012144.GA7616@tansi.org> References: <4CDC3C5E.1020108@gmx.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CDC3C5E.1020108@gmx.at> Subject: Re: [dm-crypt] Improving performance? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Krainz Cc: dm-crypt@saout.de On Thu, Nov 11, 2010 at 07:56:30PM +0100, Markus Krainz wrote: > > On 2010-11-11 19:26, Lasse Jensen wrote: >> I havent tested my current setup this way, but my old setup, RAID >> first, then encryption worked fine. > > RAID first, den ecryption works for me, too. > But testing the ecrypting drives seperately, then RAID approach failed. > What good is fast performance if the RAID 5 does not work? :D I Have not tried encytion first, but I have several 3-way RAID1 with RAID first runnign without a problem for > 2 years now. (It is partition RAID1, only 3 disks involved.) I would imagine that encryption-first is a bit of a risk until the kernel barriers have been cleaned up. BTW, I see significantly better behavior with 2.6.36. Hope they manage to clean this mess up by 2.6.37. The kernel used to be tunable to not slow to a crawl when writing large amounts of data onto slow devices. One of the ugly secrets up to 2.6.35. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier