linux-kernel - Re: [RFC][PATCH 0/7] UBI checkpointing support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120308090835.032fe13a@pixies.home.jungo.com>
Date:	Thu, 8 Mar 2012 09:08:35 +0200
From:	Shmulik Ladkani <shmulik.ladkani@...il.com>
To:	Richard Weinberger <rw@...utronix.de>
Cc:	dedekind1@...il.com, tglx@...utronix.de,
	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
	tim.bird@...sony.com
Subject: Re: [RFC][PATCH 0/7] UBI checkpointing support

On Wed, 07 Mar 2012 22:19:00 +0100 Richard Weinberger <rw@...utronix.de> wrote:
> >> All these operations scan a limited number of erase blocks which makes
> >> the UBI init O(1) and independent of the device size.
> >
> > Well, is it really true? The larger is the flash the more you read and
> > process anyway, and it is still linear, but the multiplier becomes very
> > small, so this is a huge improvement.
> 
> Yes. :)
> 
> Using checkpointing UBI only has to scan a fixed (independent of the 
> flash size!) number of blocks.

But doesn't the CP data (sorry, UBIUBI data :) need to have one
'struct ubi_cp_ec' descriptor for each used/free PEB, and as such the
maximum number of 'ubi_cp_ec' descriptors is total device PEBs, meaning
CP data is still linearly scaled to device size (with a very small
multiplier)?

Regards,
Shmulik
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/