From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030577Ab2CGWJY (ORCPT ); Wed, 7 Mar 2012 17:09:24 -0500 Received: from www.linutronix.de ([62.245.132.108]:39057 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030251Ab2CGWJV (ORCPT ); Wed, 7 Mar 2012 17:09:21 -0500 Date: Wed, 7 Mar 2012 23:09:18 +0100 (CET) From: Thomas Gleixner To: Richard Weinberger cc: dedekind1@gmail.com, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, tim.bird@am.sony.com Subject: Re: [RFC][PATCH 1/7] MTD: UBI: Add checkpoint on-chip layout In-Reply-To: <4F57CCF4.6040902@linutronix.de> Message-ID: References: <1329250006-22944-1-git-send-email-rw@linutronix.de> <1329250006-22944-2-git-send-email-rw@linutronix.de> <1331136589.3463.3.camel@sauron.fi.intel.com> <4F57CCF4.6040902@linutronix.de> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 7 Mar 2012, Richard Weinberger wrote: > Am 07.03.2012 17:09, schrieb Artem Bityutskiy: > > On Tue, 2012-02-14 at 21:06 +0100, Richard Weinberger wrote: > > > Specify the on-chip checkpoint layout. > > > The checkpoint consists of two major parts. > > > A super block (identified via UBI_CP_SB_VOLUME_ID) and > > > zero or more data blocks (identified via UBI_CP_DATA_VOLUME_ID). > > > Data blocks are only used if whole checkpoint information does not fit > > > into the super block. > > > > And superblock is also a more or less standard name used by file-system. > > I easily imagine difficulties and confusion when discussing UBIFS and > > UBI and mixing UBI and UBIFS supersblocks up. IMHO, anything unique is > > much better, even if it does not make much sense. E.g., "boss block" or > > "pomo block" (pomo = boss in Finnish). > > > > Would you consider picking a different name as well please? > > > > Will do. What about FASTMAP ? That's what the whole story is about. Building the logical/physical mappings (fast). Then call the "super block" FASTMAP_REF and the data stuff FASTMAP_DATA. That's the sanest I could come up with aside of smuggling in my favourite buzzword ROADMAP :) Of course we could stay with latin and name it: UBIUBI. ubiubi is latin for: where the heck is it, but I guess that's stretching it a bit :) Thanks, tglx