Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756097AbYH0NRx (ORCPT ); Wed, 27 Aug 2008 09:17:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754959AbYH0NRp (ORCPT ); Wed, 27 Aug 2008 09:17:45 -0400 Received: from ns.firmix.at ([62.141.48.66]:1852 "EHLO ns.firmix.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754916AbYH0NRp (ORCPT ); Wed, 27 Aug 2008 09:17:45 -0400 Subject: Re: [Bug #11342] Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected From: Bernd Petrovitsch To: Parag Warudkar Cc: Linus Torvalds , Adrian Bunk , Rusty Russell , "Alan D. Brunelle" , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Andrew Morton , Arjan van de Ven , Ingo Molnar , linux-embedded@vger.kernel.org In-Reply-To: References: <20080826183051.GB10925@cs181140183.pp.htv.fi> <20080826205916.GB11734@cs181140183.pp.htv.fi> <1219827609.30209.29.camel@spike.firmix.at> Content-Type: text/plain Organization: Firmix Software GmbH Date: Wed, 27 Aug 2008 15:17:12 +0200 Message-Id: <1219843032.30209.51.camel@spike.firmix.at> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-8.el5_2.2) Content-Transfer-Encoding: 7bit X-Firmix-Scanned-By: MIMEDefang 2.56 on ns.firmix.at X-Firmix-Spam-Score: -2.344 () AWL,BAYES_00,FORGED_RCVD_HELO,SPF_HELO_PASS,SPF_PASS X-Firmix-Spam-Status: No, hits=-2.344 required=5 X-Spam-Score: -2.344 () AWL,BAYES_00,FORGED_RCVD_HELO,SPF_HELO_PASS,SPF_PASS X-Firmix-Envelope-From: X-Firmix-Envelope-To: Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2002 Lines: 45 On Wed, 2008-08-27 at 08:56 -0400, Parag Warudkar wrote: > On Wed, Aug 27, 2008 at 5:00 AM, Bernd Petrovitsch wrote: > > They probably gave the idea pretty soon because you need to > > rework/improve large parts of the kernel + drivers (and that has two > > major problems - it consumes a lot of man power for "no new features and > > everything must be completely tested again"[0] and it adds new risks). > > And that is practically impossible if one sells "stable driver APIs" for > > 3rd party (commercial) drivers because these must be changed too. > > But not many embedded Linux arches support 4K stacks like Adrian What is an "embedded Linux arch"? Personally I encountered i386, ARM, MIPS and PPC in the embedded world. > pointed out earlier. > So the same (lot of man power requirement) would apply to Linux. Of course. Look at the amount of work done by lots of people in that area (including stack frame size reductions) and on-going discussions. > Sure it will be good - but how reasonable it is to attempt it and how > reliably it will work under all conceived loads - those are the > questions. If you "develop" an embedded system (which is partly system integration of existing apps) to be installed in the field, you don't have that many conceivable work loads compared to a desktop/server system. And you have a fixed list of drivers and applications. A usual approach is to run stress tests on several (or all) subsystems/services/... in parallel and if the device survives it functioning correctly, it is at least good enough. Bernd -- Firmix Software GmbH http://www.firmix.at/ mobil: +43 664 4416156 fax: +43 1 7890849-55 Embedded Linux Development and Services -- 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/