From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.saout.de (Postfix) with ESMTPS
	for <dm-crypt@saout.de>; Wed, 21 Oct 2009 17:40:28 +0200 (CEST)
Received: from list by lo.gmane.org with local (Exim 4.50) id 1N0dG5-0001py-Ez
	for dm-crypt@saout.de; Wed, 21 Oct 2009 17:37:53 +0200
Received: from 84.119.83.175 ([84.119.83.175])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <dm-crypt@saout.de>; Wed, 21 Oct 2009 17:37:53 +0200
Received: from gebi by 84.119.83.175 with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <dm-crypt@saout.de>; Wed, 21 Oct 2009 17:37:53 +0200
From: Michael Gebetsroither <gebi@sbox.tugraz.at>
Date: Wed, 21 Oct 2009 17:34:50 +0200
Message-ID: <hbn9mt$bqr$1@ger.gmane.org>
References: <a947659077bae400d3d5928057b26575.squirrel@ssl.verfeiert.org>
	<20090919004502.GB31184@tansi.org> <1253360741.4317.15.camel@HansWurst>
	<bb145bd20910210348g3238d4b8p2716e79cc2cb86e7@mail.gmail.com>
	<Mahogany-0.67.1-5524-20091021-125917.00@ming.ricknet.net>
	<bb145bd20910210805s2dd781a3t5ccb347b652c95c0@mail.gmail.com>
	<Mahogany-0.67.1-5524-20091021-170829.00@ming.ricknet.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: news <news@ger.gmane.org>
Subject: Re: [dm-crypt] md-raid5+lvm+dm-crypt+kvm: one streaming write
	starves all reads
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

* Rick Moritz <rahvin@gmail.com> wrote:
>> > Is the advantage still there, when you've only got one core available?
>> 
>> Is there a way to tell the kernel to disable one core at boot? The
>> BIOS doesn't have an option for it on this board.
>
> You should be able to build a non-SMP kernel - that ought to restrict the kernel threads to serial execution.

booting with maxcpus=0 or nosmp should do the same.

michael
-- 
It's already too late!