linux-kernel - Re: [PATCH 14/50] sched: Set the scan rate proportional to the memory usage of the task being scanned

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: <20130916154035.GE22421@suse.de>
Date:	Mon, 16 Sep 2013 16:40:35 +0100
From:	Mel Gorman <mgorman@...e.de>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Rik van Riel <riel@...hat.com>,
	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>,
	Andrea Arcangeli <aarcange@...hat.com>,
	Johannes Weiner <hannes@...xchg.org>,
	Linux-MM <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 14/50] sched: Set the scan rate proportional to the
 memory usage of the task being scanned

On Mon, Sep 16, 2013 at 05:18:22PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 10, 2013 at 10:31:54AM +0100, Mel Gorman wrote:
> > @@ -860,9 +908,14 @@ void task_numa_fault(int node, int pages, bool migrated)
> >  	 * If pages are properly placed (did not migrate) then scan slower.
> >  	 * This is reset periodically in case of phase changes
> >  	 */
> > -        if (!migrated)
> > -		p->numa_scan_period = min(sysctl_numa_balancing_scan_period_max,
> > +        if (!migrated) {
> > +		/* Initialise if necessary */
> > +		if (!p->numa_scan_period_max)
> > +			p->numa_scan_period_max = task_scan_max(p);
> > +
> > +		p->numa_scan_period = min(p->numa_scan_period_max,
> >  			p->numa_scan_period + jiffies_to_msecs(10));
> 
> So the next patch changes the jiffies_to_msec() thing.. is that really
> worth a whole separate patch?
> 

No, I can collapse them.

> Also, I really don't believe any of that is 'right', increasing the scan
> period by a fixed amount for every !migrated page is just wrong.
> 

At the moment Rik and I are both looking at adapting the scan rate based
on whether the faults trapped since the last scan window were local or
remote faults. It should be able to sensibly adapt the scan rate
independently of the RSS of the process.

-- 
Mel Gorman
SUSE Labs
--
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/