Each page is supposed to have an owner - the container
that touched the page first. The owner stays alive during
the page lifetime even if the task that touched the page
dies or moves to another container.
This ownership is the forerunner for the "fair" page sharing
accounting, in which page has a
On Wed, 30 May 2007 19:28:04 +0400
Pavel Emelianov <[EMAIL PROTECTED]> wrote:
> +#ifdef CONFIG_RSS_CONTAINER
> +#define page_container(page) (page->rss_container)
> +#else
> +#define page_container(page) (NULL)
> +#endif
static inline C functions are nicer.
-
To unsubscribe from this list: send t
Each page is supposed to have an owner - the container
that touched the page first. The owner stays alive during
the page lifetime even if the task that touched the page
dies or moves to another container.
This ownership is the forerunner for the "fair" page sharing
accounting, in which page has a
Jean-Pierre Dion wrote:
> Hi Pavel,
>
> I have been implied in the work for the
> memory controller of res groups a few months ago.
>
> I see that you propose to modify the struct
> page to point to rss container struct.
> This has made some debate because of the struct
> page size increase, but
Hi Pavel,
I have been implied in the work for the
memory controller of res groups a few months ago.
I see that you propose to modify the struct
page to point to rss container struct.
This has made some debate because of the struct
page size increase, but this allows a quicker
scan to reclaim pag
Each page is supposed to have an owner - the container
that touched the page first. The owner stays alive during
the page lifetime even if the task that touched the page
dies or moves to another container.
This ownership is the forerunner for the "fair" page sharing
accounting, in which page has a
6 matches
Mail list logo