Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933058AbXB0MVH (ORCPT ); Tue, 27 Feb 2007 07:21:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933065AbXB0MVG (ORCPT ); Tue, 27 Feb 2007 07:21:06 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:37716 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933057AbXB0MVF (ORCPT ); Tue, 27 Feb 2007 07:21:05 -0500 Date: Tue, 27 Feb 2007 13:13:28 +0100 From: Ingo Molnar To: Evgeniy Polyakov Cc: Theodore Tso , Linus Torvalds , Ulrich Drepper , linux-kernel@vger.kernel.org, Arjan van de Ven , Christoph Hellwig , Andrew Morton , Alan Cox , Zach Brown , "David S. Miller" , Suparna Bhattacharya , Davide Libenzi , Jens Axboe , Thomas Gleixner Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3 Message-ID: <20070227121328.GA18565@elte.hu> References: <45DCD9E5.2010106@redhat.com> <20070222074044.GA4158@elte.hu> <20070222113148.GA3781@2ka.mipt.ru> <20070226172812.GC22454@2ka.mipt.ru> <20070226195416.GA11188@elte.hu> <20070227102832.GC23170@2ka.mipt.ru> <20070227115221.GJ8154@thunk.org> <20070227121116.GA31597@2ka.mipt.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070227121116.GA31597@2ka.mipt.ru> User-Agent: Mutt/1.4.2.2i X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.0.3 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1005 Lines: 27 * Evgeniy Polyakov wrote: > > [...] But it is true that for most kernel programmers, threaded > > programming is much easier to understand, and we need to engineer > > the kernel for what will be maintainable for the majority of the > > kernel development community. > > I understand that - and I totally agree. why did you then write, just one mail ago, the exact opposite: > And debugging state machine code has exactly the same complexity as > debugging multi-threading code - if not less... the kernel /IS/ multi-threaded code. which statement of yours is also patently, absurdly untrue. Multithreaded code is harder to debug than process based code, but it is still a breeze compared to complex state-machines... Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/