linux-kernel - Re: [RFC][PATCH 0/5] Memory controller soft limit patches (v9)

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: <20090715053222.GH24034@balbir.in.ibm.com>
Date:	Wed, 15 Jul 2009 11:02:22 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	linux-mm@...ck.org, lizf@...fujitsu.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 0/5] Memory controller soft limit patches (v9)

* KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> [2009-07-15 14:28:19]:

> > * Balbir Singh <balbir@...ux.vnet.ibm.com> [2009-07-10 18:29:50]:
> > 
> > > 
> > > From: Balbir Singh <balbir@...ux.vnet.ibm.com>
> > > 
> > > New Feature: Soft limits for memory resource controller.
> > > 
> > > Here is v9 of the new soft limit implementation. Soft limits is a new feature
> > > for the memory resource controller, something similar has existed in the
> > > group scheduler in the form of shares. The CPU controllers interpretation
> > > of shares is very different though. 
> > >
> > 
> > If there are no objections to these patches, could we pick them up for
> > testing in mmotm. 
> 
> Sorry, I haven't review this patch series. please give me few days.
>

Sure, could you see if the reclaim bits are better now. 

-- 
        Thanks,
	Balbir
--
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/