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: <20090715133324.e4683ef2.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Wed, 15 Jul 2009 13:33:24 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	balbir@...ux.vnet.ibm.com
Cc:	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	lizf@...fujitsu.com, linux-kernel@...r.kernel.org,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Subject: Re: [RFC][PATCH 0/5] Memory controller soft limit patches (v9)

On Wed, 15 Jul 2009 09:38:11 +0530
Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:

> * 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. 
> 

If any, will be fixed up in mmotm. About behavior, I don't have more things
than I've said. (dealying kswapd is not very good.)

But plz discuss with Vladislav Buzov about implementation details of [2..3/5].
==
[PATCH 1/2] Resource usage threshold notification addition to res_counter (v3)

It seems there are multiple functionalities you can shere with them.

 - hierarchical threshold check
 - callback or notify agaisnt threshold.
 etc..

I'm very happy if all messy things around res_counter+hierarchy are sorted out
before diving into melting pot. I hope both of you have nice interfaces and
keep res_counter neat.

Thanks,
-Kame

--
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/