[Devel] Re: [PATCH 1/2] [RFC] Add file f_flags to cgroup write_string ops

[Balbir Singh]

* KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> [2009-10-27 09:03:11]:

> On Mon, 26 Oct 2009 08:15:29 -0700
> Matt Helsley <matthltc at us.ibm.com> wrote:
> 
> > cgroup subsystems may find the O_APPEND and O_NONBLOCK flags useful
> > in determining the way they handle writes. For now only pass these
> > flags through the write_string op.
> > 
> > A subsequent patch will make use of the O_NONBLOCK flag in the
> > cgroup freezer write_string op.
> > 
> > Signed-off-by: Matt Helsley <matthltc at us.ibm.com>
> > Cc: Nathan Lynch <ntl at pobox.com>
> > Cc: Paul Menage <menage at google.com>
> > Cc: Li Zefan <lizf at cn.fujitsu.com>
> > 
> > (Cc'ing mem controller maintainers in case they find this useful..)
> > Cc: Balbir Singh <balbir at linux.vnet.ibm.com>
> > Cc: Pavel Emelyanov <xemul at openvz.org>
> > Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com>
> 
> Hmm, maybe useful if we decided to add memory.drop_memory or some...
> But now, we have no plan to add backup thread(for asynchronous job).
> or some trylock ops.
> Anyway, no objection from me if you want this.
> 

I see no issues as well, but no use at the moment right away.


-- 
	Balbir
_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers