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: <9156032.1214874373850.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Tue, 1 Jul 2008 10:06:13 +0900 (JST)
From:	kamezawa.hiroyu@...fujitsu.com
To:	kamezawa.hiroyu@...fujitsu.com
Cc:	Hugh Dickins <hugh@...itas.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Rik van Riel <riel@...hat.com>,
	Lee Schermerhorn <lee.schermerhorn@...com>,
	Balbir Singh <balbir@...ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: Re: Re: [RFC][PATCH] memcg: change shmem handler.

----- Original Message -----
Sorry..a bit more words.
>>Is that a good thing?  If we really decide that globally we
>>need such a counter, then fine for memcg to follow; but I've
>>not yet heard it asked for.
>After swap-controller is introduced, I can imagine there will be a
>swap-full/swap-less cgroup. And shmem will be able to be swapped out.
                                          not
>memcg handles limit of memory usage and Admin/Middleware will want to
>know current limit is good or bad. So, showing amount of tmpfs 
>will be good (It's now shown as Cache...a pages easily kicked out ;)
>
I'm not sure but how this seems under memcg in which DataBase runs.

Now.
   - anon
   - cache (including DataBase's shmem)
After
   - anon
   - cache (file cache)
   - shmem (DataBase's working area)

not good ?

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ