[lkml]   [2006]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjectmemory resource accounting (was Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller)
    Martin Bligh wrote:
    > Rohit Seth wrote:

    Hi guys, let me make a fool of myself and jump in this thread...

    >> I think there is lot of simplicity and value add by charging one
    >> container (even unfairly) for one resource completely. This puts the
    >> onus on system admin to set up the containers appropriately.
    > It also saves you from maintaining huge lists against each page.
    > Worse case, you want to bill everyone who opens that address_space
    > equally. But the semantics on exit still suck.
    > What was Alan's quote again? "unfair, unreliable, inefficient ...
    > pick at least one out of the three". or something like that.

    What's the sucking semantics on exit? I haven't looked much at the
    existing memory controllers going around, but the implementation I
    imagine looks something like this (I think it is conceptually similar
    to the basic beancounters idea):

    - anyone who allocates a page for anything gets charged for that page.
    Except interrupt/softirq context. Could we ignore these for the moment?

    This does give you kernel (slab, pagetable, etc) allocations as well as
    userspace. I don't like the idea of doing controllers for inode cache
    and controllers for dentry cache, etc, etc, ad infinitum.

    - each struct page has a backpointer to its billed container. At the mm
    summit Linus said he didn't want back pointers, but I clarified with him
    and he isn't against them if they are easily configured out when not using
    memory controllers.

    - memory accounting containers are in a hierarchy. If you want to destroy a
    container but it still has billed memory outstanding, that gets charged
    back to the parent. The data structure itself obviously still needs to
    stay around, to keep the backpointers from going stale... but that could
    be as little as a word or two in size.

    The reason I like this way of accounting is that it can be done with a couple
    of hooks into page_alloc.c and an ifdef in mm.h, and that is the extent of
    the impact on core mm/ so I'd be against anything more intrusive unless this
    really doesn't work.

    SUSE Labs, Novell Inc.
    Send instant messages to your online friends

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-08-08 16:23    [W:0.028 / U:13.736 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site