[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070227121328.GA18565@elte.hu>
Date: Tue, 27 Feb 2007 13:13:28 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Evgeniy Polyakov <johnpol@....mipt.ru>
Cc: Theodore Tso <tytso@....edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ulrich Drepper <drepper@...hat.com>,
linux-kernel@...r.kernel.org,
Arjan van de Ven <arjan@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@....com.au>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Zach Brown <zach.brown@...cle.com>,
"David S. Miller" <davem@...emloft.net>,
Suparna Bhattacharya <suparna@...ibm.com>,
Davide Libenzi <davidel@...ilserver.org>,
Jens Axboe <jens.axboe@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3
* Evgeniy Polyakov <johnpol@....mipt.ru> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists