IETF Logo Mail Archive

[Roll] draft-rahul-roll-rpl-observations-00 Section 2.1: Wear leveling

Carsten Bormann <cabo@tzi.org> Thu, 22 March 2018 10:28 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFE38120726 for <roll@ietfa.amsl.com>; Thu, 22 Mar 2018 03:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15CcELNgLzM8 for <roll@ietfa.amsl.com>; Thu, 22 Mar 2018 03:28:46 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A896A1201F2 for <roll@ietf.org>; Thu, 22 Mar 2018 03:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w2MASgQt001106 for <roll@ietf.org>; Thu, 22 Mar 2018 11:28:42 +0100 (CET)
Received: from [IPv6:2001:638:708:18::31] (unknown [IPv6:2001:638:708:18::31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 406NDp539nzDXDh; Thu, 22 Mar 2018 11:28:42 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
X-Mao-Original-Outgoing-Id: 543407319.0684201-683a28a463e6bebd9993d3896dc726cd
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 22 Mar 2018 10:28:41 +0000
Message-Id: <8EC2893F-731B-439D-86FE-984505349D8D@tzi.org>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/cWVYt_COyVyQf0Qr2prnH9EPkcI>
Subject: [Roll] draft-rahul-roll-rpl-observations-00 Section 2.1: Wear leveling
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 10:28:48 -0000

Today, at the mike, I asked about wear leveling.

The numbers in 2.1 seem to assume you do a full erase/write cycle per store operation.
That is not a good way to use Flash storage.  Obviously, for true wear leveling you need a bit more flash space (and a bit more code, which also needs flash space), but then there already are other items that you want to commit to stable storage on a somewhat regular basis.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email