Re: [PATCH 5/8] RSS accounting hooks over the code

On Wed, 30 May 2007 19:34:18 +0400
Pavel Emelianov <[email protected]> wrote:

> As described above, pages are charged to their first touchers.
> The first toucher is determined using pages' _mapcount 
> manipulations in rmap calls.
> 
> Page is charged in two stages:
> 1. preparation, in which the resource availability is checked.
>    This stage may lead to page reclamation, thus it is performed
>    in a "might-sleep" places;
> 2. the container assignment to page. This is done in an atomic
>    code that handles races between multiple touchers.

I suppose we need to think about what to do about higher-order pages, and
compound pages, and hugetlb memory.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 5/8] RSS accounting hooks over the code
    • From: Balbir Singh <[email protected]>

• References:
  • [PATCH 0/8] RSS controller based on process containers (v3)
    • From: Pavel Emelianov <[email protected]>
  • [PATCH 5/8] RSS accounting hooks over the code
    • From: Pavel Emelianov <[email protected]>

• Prev by Date: Re: [PATCH 4/8] RSS container core
• Next by Date: Re: [PATCH 7/8] Scanner changes needed to implement per-container scanner
• Previous by thread: [PATCH 5/8] RSS accounting hooks over the code
• Next by thread: Re: [PATCH 5/8] RSS accounting hooks over the code
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]