linux-kernel - Re: [PATCH 0/8] idle page tracking / working set estimation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKTCnzkzdQgut96NZf3Mi2kpOWW7N3qeybets5AHy7Gp8Wj_HQ@mail.gmail.com>
Date:	Tue, 27 Sep 2011 15:33:10 +0530
From:	Balbir Singh <bsingharora@...il.com>
To:	Michel Lespinasse <walken@...gle.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Dave Hansen <dave@...ux.vnet.ibm.com>,
	Andrea Arcangeli <aarcange@...hat.com>,
	Rik van Riel <riel@...hat.com>,
	Johannes Weiner <jweiner@...hat.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Hugh Dickins <hughd@...gle.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Michael Wolf <mjwolf@...ibm.com>
Subject: Re: [PATCH 0/8] idle page tracking / working set estimation

On Sat, Sep 17, 2011 at 9:09 AM, Michel Lespinasse <walken@...gle.com> wrote:
> Please comment on the following patches (which are against the v3.0 kernel).
> We are using these to collect memory utilization statistics for each cgroup
> accross many machines, and optimize job placement accordingly.
>
> The statistics are intended to be compared accross many machines - we
> don't just want to know which cgroup to reclaim from on an individual
> machine, we also need to know which machine is best to target a job onto
> within a large cluster. Also, we try to have a low impact on the normal
> MM algorithms - we think they already do a fine job balancing resources
> on individual machines, so we are not trying to mess up with that here.
>
> Patch 1 introduces no functionality; it modifies the page_referenced API
> so that it can be more easily extended in patch 3.
>
> Patch 2 documents the proposed features, and adds a configuration option
> for these. When the features are compiled in, they are still disabled
> until the administrator sets up the desired scanning interval; however
> the configuration option seems necessary as the features make use of
> 3 extra page flags - there is plenty of space for these in 64-bit builds,
> but less so in 32-bit builds...
>
> Patch 3 introduces page_referenced_kstaled(), which is similar to
> page_referenced() but is used for idle page tracking rather than
> for memory reclaimation. Since both functions clear the pte_young bits
> and we don't want them to interfere with each other, two new page flags
> are introduced that track when young pte references have been cleared by
> each of the page_referenced variants.

Sorry, I have trouble parsing this sentence, could you elaborate on "when"?


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