From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13923 invoked by alias); 3 Nov 2003 14:38:54 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 13916 invoked from network); 3 Nov 2003 14:38:54 -0000 Received: from unknown (HELO proxy.baslerweb.com) (145.253.187.130) by sources.redhat.com with SMTP; 3 Nov 2003 14:38:54 -0000 Received: from comm1.baslerweb.com ([172.16.13.2]) by proxy.baslerweb.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Mon, 3 Nov 2003 15:36:40 +0100 Received: from 172.16.13.253 (VCLINUX-1 [172.16.13.253]) by comm1.baslerweb.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 32J5J1SQ; Mon, 3 Nov 2003 15:38:43 +0100 From: Thomas Koeller Organization: Basler AG To: ecos-discuss@sources.redhat.com Date: Mon, 03 Nov 2003 14:38:00 -0000 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311031538.57806.thomas.koeller@baslerweb.com> Subject: [ECOS] jffs2 memory allocation X-SW-Source: 2003-11/txt/msg00008.txt.bz2 As has been stated earlier (see http://ecos.sourceware.org/ml/ecos-discuss/2003-10/msg00247.html), the memory allocation routines used by the ecos port of jffs2 could be improved by using a fixed- size block allocator instead of the current malloc()-based scheme. This could be achieved in two different ways: A new set of allocator routines could be added to the jffs2 package, to either replace or complement the existing functions. Or one could simply add a 'weak' attribute to the existing functions, so the application could redefine them. The first approach yields something that is easy to use, but there can only be limited control of the allocation process (by means of configuration parameters). The second approach requires more work to be done by the user, but also gives better control, which may be beneficial. For example, I might want to use a separate heap for this purpose. I feel a bit uncertain about which way to go, so I'd welcome any comments. tk -------------------------------------------------- Thomas Koeller, Software Development Basler Vision Technologies An der Strusbek 60-62 22926 Ahrensburg Germany Tel +49 (4102) 463-162 Fax +49 (4102) 463-239 mailto:thomas.koeller@baslerweb.com http://www.baslerweb.com ============================== -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss