lkml.org 
[lkml]   [2002]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [lkcd-devel] Re: What's left over.

    On 7 Nov 2002, Eric W. Biederman wrote:
    >
    > In staging the image we allocate a whole pile of pages, and keep them
    > locked in place. Waiting for years potentially until the machine
    > reboots or panics. This memory is not accounted for anywhere so no
    > one can see that we have it allocated, which makes debugging hard.

    So how about facing the fact that my "vmalloc()" approach actually solves
    all these issues. The memory is visible to the rest of the system (few
    things care about it right now, but it _is_ accounted for and things like
    /dev/kmem will actually see it etc).

    And the vmalloc() approach is even portable, so one of the two phases is
    something that is totally generic (and the second phase is almost totally
    architecture-dependent anyway).

    Linus

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

    \
     
     \ /
      Last update: 2005-03-22 13:30    [W:2.319 / U:0.300 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site