From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.nokia.com ([192.100.122.230] helo=mgw-mx03.nokia.com) by bombadil.infradead.org with esmtps (Exim 4.69 #1 (Red Hat Linux)) id 1LUcSK-0003zx-JP for linux-mtd@lists.infradead.org; Wed, 04 Feb 2009 07:45:59 +0000 Subject: Re: Regarding UBI scalability From: Artem Bityutskiy To: Corentin Chary In-Reply-To: <71cd59b00902030313v47c2861anb8078e1f75de7eeb@mail.gmail.com> References: <31956721.196931233319535527.JavaMail.weblogic@epml10> <1233567078.7085.62.camel@localhost.localdomain> <618F1BB69C6C43C895C260C527C4F159@sisodomain.com> <4986D3F6.5030208@nokia.com> <1233572259.7085.64.camel@localhost.localdomain> <4986D677.3020500@nokia.com> <71cd59b00902021544w594d4acandc0183bc523aafb0@mail.gmail.com> <1233658015.24809.105.camel@localhost.localdomain> <71cd59b00902030313v47c2861anb8078e1f75de7eeb@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 04 Feb 2009 09:45:51 +0200 Message-Id: <1233733551.5138.33.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: Amit Kumar Sharma , "linux-mtd@lists.infradead.org" , Adrian Hunter , "brij.singh@samsung.com" Reply-To: dedekind@infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2009-02-03 at 12:13 +0100, Corentin Chary wrote: > On Tue, Feb 3, 2009 at 11:46 AM, Artem Bityutskiy > wrote: > > On Tue, 2009-02-03 at 00:44 +0100, Corentin Chary wrote: > >> I was wondering how it is possible to get atomic operations using such tables ? > >> The first thing that come to my mind is TFAT (two tables, one for > >> operation in progress, > >> the other considered as always "valid"). But I'm not sure it' the good > >> way to do such a thing. > > > > Journal + commit mechanisms should allow doing this. > > I'm asking some other questions, because in UFFS we are working on > something like that, but not for UBI2. But if I can help for UBI2, > I'll. > > A journal node, would probably take less than 16 B. With min_io_size > >= 512 B (sometime 2KB), a journal for map/unmap operation will take > some time before being written. Well, to guarantee integrity, I do not see any other solution but doing 2x2KiB writes on 2KiB-page NAND: start update (1), (write the LEB somewhere), end update (2), (erase the old PEB). That's the price you pay. -- Best regards, Artem Bityutskiy (Битюцкий Артём)