From owner-freebsd-small@FreeBSD.ORG Sun May 28 10:17:24 2006 Return-Path: X-Original-To: small@freebsd.org Delivered-To: freebsd-small@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CA6516AC62 for ; Sun, 28 May 2006 10:05:29 +0000 (UTC) (envelope-from james@wgold.demon.co.uk) Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97C1343D46 for ; Sun, 28 May 2006 10:05:28 +0000 (GMT) (envelope-from james@wgold.demon.co.uk) Received: from wgold.demon.co.uk ([158.152.96.124] helo=thor) by anchor-post-33.mail.demon.net with esmtp (Exim 4.42) id 1FkI9G-00043w-9v; Sun, 28 May 2006 10:05:26 +0000 Received: from 127.0.0.1 by thor ([127.0.0.1] running VPOP3) with SMTP; Sun, 28 May 2006 10:20:26 +0100 From: "James Mansion" To: "marty fouts" Date: Sun, 28 May 2006 10:20:22 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <9f7850090605271000j524d6a35gfa3f6df1f0ed59f5@mail.gmail.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Server: VPOP3 V1.5.0k - Registered Cc: Alexander Leidinger , Poul-Henning Kamp , Andrew Atrens , small@freebsd.org Subject: RE: FreeBSD's embedded agenda X-BeenThere: freebsd-small@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2006 10:17:29 -0000 >Experience suggests that wear leveling does matter in this market, but >that fairly simple wear leveling can be very effective. Can I ask why? I mmay be a very bed person to talk about phones, because I have a 6-year-old Seimens I chose for battery life and the first thing I did was disable IrDa and WAP. It doesn't have a camera. ;-) And I've never sent a text. I can see that you might want to store 'call missed' messages and incoming texts, and phone lists etc, and maybe store a photo or two, but these things are either low-frequency or user-driven and very low frequency. Where are all the updates coming from? My phone is the oldest of any of the people I've worked with in my last two contracts. Its well out of warranty, and I suspect its out of its design life too. If you take Linux as an example, even without physical wear- levelling you can run for a long, long time if you run with noatime and defer physical updates with laptop mode. Of course, laptop mode can leave you exposed, but I would hope that soft-updates can effectively help out here in terms of a strategy to write blocks in an order that's sane.