[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Policy-based memory allocations (was Re: RFC: 1.97 roadmap)

From: Vladimir 'phcoder' Serbinenko
Subject: Re: Policy-based memory allocations (was Re: RFC: 1.97 roadmap)
Date: Thu, 13 Aug 2009 23:01:48 +0200

> But available memory is several orders of magnitude bigger than the largest
> block a loader will need.  So is this really an issue?
It's not always the case. Two examples
1) Solaris. At least some distributions of solaris use a big (70 MiB
compressed, around 200 MiB compressed) initrd which has to be loaded
as multiboot module in a single chunk. This puts biggest needed chunk
in the same order of magnitude as RAM available on some smaller
2) XNU hibernating. It requires booter to load hibernating image in a
single chunk. Even though it's compressed it can easily be 50% of
total RAM or more
> --
> Robert Millan
>  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
>  how) you may access your data; but nobody's threatening your freedom: we
>  still allow you to remove your data and not access it at all."
> _______________________________________________
> Grub-devel mailing list
> address@hidden

Vladimir 'phcoder' Serbinenko

Personal git repository:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]