On 7/9/07, Mitch Bradley <[EMAIL PROTECTED]> wrote:
> If you fill the FLASH with useful data, you cannot hibernate.
We could imagine alternate UIs, where hibernation was an optional,
rather than mandatory, feature. This would allow us to fail to
hibernate under disk-full or large-memory condition
Bernardo Innocenti wrote:
> Mitch Bradley wrote:
>
>> We probably don't want to store the data in JFFS2. Better to
>> partition the NAND FLASH.
>
> Partitioning makes things easier, but it's a big waste of space.
> Ideally, one should be able to fill the flash with useful data.
>
If you fill the
Mitch Bradley wrote:
> We probably don't want to store the data in JFFS2. Better to partition
> the NAND FLASH.
Partitioning makes things easier, but it's a big waste of space.
Ideally, one should be able to fill the flash with useful data.
--
// Bernardo Innocenti
\X/ http://www.codewiz
Bernardo Innocenti wrote:
> Jordan Crouse wrote:
>
>
>> I agree - the suspend to disk code in Linux is already quite mature and
>> ready for use - it only saves the pages it needs to. The question here
>> isn't so much how to implement STD, since the concep
Jordan Crouse wrote:
> I agree - the suspend to disk code in Linux is already quite mature and
> ready for use - it only saves the pages it needs to. The question here
> isn't so much how to implement STD, since the concepts are pretty well
> understood - but rather, can we
take longer (or maybe not;
> > you trade not having to write the data out on the way down for having to
> > do more work on the way up).
>
> The existing linux suspend-to-disk does this: pages that are
> disk-backed are not duplicated, and dirty pages are written out rather
&g
On Mon, 2007-07-09 at 01:06 -0400, C. Scott Ananian wrote:
> The existing linux suspend-to-disk does this: pages that are
> disk-backed are not duplicated, and dirty pages are written out rather
> than saved dirty. There is a time penalty for doing this. Suspend2
> has supp
way down for having to
> do more work on the way up).
The existing linux suspend-to-disk does this: pages that are
disk-backed are not duplicated, and dirty pages are written out rather
than saved dirty. There is a time penalty for doing this. Suspend2
has support for page compression as well (
In any analysis, please don't bother with the B1 and B2 configurations
as those platform profiles will not be an option in the production
machines.
-walter
On 7/8/07, Mitch Bradley <[EMAIL PROTECTED]> wrote:
> Andres Salomon wrote:
> > ...
> >
> > Implementation questions:
> >
> > I'm not going t
Andres Salomon wrote:
> ...
>
> Implementation questions:
>
> I'm not going to concern myself with our B1s, for they have more ram
> and less nand. Our B2s have 128MB of ram, and 512MB of nand; B3s and
> up have 256MB of ram, and 1GB of nand. We need to figure out just
> how much space we'd need
Hi,
I'd like to figure out how feasible it would be to implement
suspend-to-disk (STD) on the XO. Currently, we support suspend-to-ram
(STR). I'm aware that suspend-to-nand would probably be a better choice
of name compared to STD, but I'd prefer to stick with the name STD for
11 matches
Mail list logo
