From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 18 Aug 2010 15:22:16 +0200 (CEST) Date: Wed, 18 Aug 2010 15:22:15 +0200 From: Heinz Diehl Message-ID: <20100818132215.GA12610@fancy-poultry.org> References: <20100817184635.GA17921@tansi.org> <4C6BC751.10506@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C6BC751.10506@redhat.com> Subject: Re: [dm-crypt] dm-crypt flush-to-disk freezes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 18.08.2010, Milan Broz wrote: > What is the IO scheduler for the underlying device? > (You can try deadline or cfq with some tuning - this is > possible to tune online). On my system, I get the best results with these (cfq): echo "1" > /sys/block/sda/queue/iosched/low_latency echo "8" > /sys/block/sda/queue/iosched/slice_idle echo "8" > /sys/block/sda/queue/iosched/quantum On some systems, things improve with slice_idle set to 0.