OpenVZ Forum


Home » Mailing lists » Devel » Re: [PATCH 2/3] memcg: put a restriction on writing memory.force_empty
Re: [PATCH 2/3] memcg: put a restriction on writing memory.force_empty [message #28191] Tue, 11 March 2008 10:15 Go to next message
Balbir Singh is currently offline  Balbir Singh
Messages: 491
Registered: August 2006
Senior Member
Li Zefan wrote:
> We can write whatever to memory.force_empty:
> 
>         echo 999 > memory.force_empty
>         echo wow > memory.force_empty
> 
> This is odd, so let's make '1' to be the only valid value.

I suspect as long as there is no unreasonable side-effect, writing 999 or wow
should be OK.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
Re: [PATCH 2/3] memcg: put a restriction on writing memory.force_empty [message #28195 is a reply to message #28191] Tue, 11 March 2008 10:23 Go to previous message
KAMEZAWA Hiroyuki is currently offline  KAMEZAWA Hiroyuki
Messages: 463
Registered: September 2006
Senior Member
On Tue, 11 Mar 2008 15:45:06 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:

> Li Zefan wrote:
> > We can write whatever to memory.force_empty:
> > 
> >         echo 999 > memory.force_empty
> >         echo wow > memory.force_empty
> > 
> > This is odd, so let's make '1' to be the only valid value.
> 
> I suspect as long as there is no unreasonable side-effect, writing 999 or wow
> should be OK.
> 
I agree with Balbir.

Thanks,
-Kame

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
Previous Topic: [PATCH 3/3] memcgoup: allow memory.failcnt to be reset
Next Topic: /etc/vz/conf/$VEID.start broken?
Goto Forum:
  


Current Time: Sat Apr 13 10:33:50 GMT 2024

Total time taken to generate the page: 0.01638 seconds