[lkml]   [2008]   [Apr]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject[PATCH 0 of 6] [RFC] another attempt at making hotplug memory and xen play together
    Hi hotplug-memory people,

    Here's my current set of WIP patches for using hotplug memory with the
    Xen balloon driver. I'm including all the xen-balloon patches so you
    have context for evaluating my hotplug-memory changes.

    The gist of the changes to the hotplug memory subsystem is:

    - split online_pages up so that users can grow the zones and actually
    online the pages as separate operations,

    - remove a bunch of duplicate definitions of online_page() (this is
    just a generally useful cleanup, and it serves to make the later
    change smaller)

    - add a section_ops structure, which defines functions to online and
    offline pages. By default this just calls the standard
    online_page() function, but the xen-balloon driver can install its
    own version which avoids onlining pages with no backing store.

    The latter is my generalization of Kamezawa-san's suggestion to put a
    hook in the x86-32 online_page() function. My problem with this idea
    is 1) how should the Xen callback know whether it should do anything
    special with a given page, and 2) what would happen if two people
    wanted to use the hook? Generally, when we want different kinds of
    the same object to have different behaviours, we add an ops structure
    and fill it out appropriately, so that's what I decided to do.
    Unfortunately threading the ops pointer through the callchain makes
    the patch a little large, but not very complex.


     \ /
      Last update: 2008-04-04 02:35    [W:0.035 / U:9.044 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site