From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 18 Aug 2010 10:31:00 +0200 (CEST) Date: Wed, 18 Aug 2010 10:31:00 +0200 From: Heinz Diehl Message-ID: <20100818083100.GB8462@fancy-poultry.org> References: <20100817184635.GA17921@tansi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100817184635.GA17921@tansi.org> 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 17.08.2010, Arno Wagner wrote: > What is the current take on this problem? Any fix > known or expected for the near future? I don't know, and I'm not a VM proff either. That said, does it improve things when you write e.g. the following in your sysctl.conf: vm.dirty_ratio = 10 vm.dirty_background_ratio = 5 Or you could go even lower using vm.dirty_background_bytes = 134217728 vm.dirty_bytes = 268435456 (but then without setting vm.dirty_ratio and vm.dirty_background). It causes pdflush to write data more frequently and in smaller amounts, thus reducing blocking via disk i/o.