Linux Container Development
 help / color / mirror / Atom feed
From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: KAMEZAWA Hiroyuki
	<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: About bio-cgroup
Date: Wed, 29 Oct 2008 14:32:29 +0530	[thread overview]
Message-ID: <490826A5.2050003@linux.vnet.ibm.com> (raw)
In-Reply-To: <20081029172918.71995f7a.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>

KAMEZAWA Hiroyuki wrote:
> On Wed, 29 Oct 2008 17:07:18 +0900 (JST)
> Hirokazu Takahashi <taka-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org> wrote:
> 
>> Hi,
>>
>>> Hi Ryo,
>>>
>>> The page_cgroup seems to be stable in the latest kernel.
>>> I'd like to know whether you have a plan or schedule to release
>>> a new version of bio-cgroup against latest kernel.
>> I have a plan on doing this.
>>
>> I thought I would start to implement it once the implementation of
>> memory cgroup got almost done. If you say the code of page_cgroup is
>> fixed, I'll start it from now on. I guess it'll be done in two weeks.
>>
> 
> code to page_cgroup itself will not be changed. (I hope)
> possible change will be
>   - new flags
>   - support to SwapCache
>   - swap_cgroup support (will be done independenly from page_cgroup.)
> 
> API of
>    lookup_page_cgroup()
>    lock_page_cgroup()
>    PCG_USED bit
> 
> will not change, I think.

I think you should not wait for stabilization, rather build on mmotm (-mm). Use
it and complain if it changes too often or becomes unusable for you.

-- 
	Balbir

  parent reply	other threads:[~2008-10-29  9:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  2:14 About bio-cgroup Gui Jianfeng
     [not found] ` <4907C6F6.8040907-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-10-29  8:07   ` Hirokazu Takahashi
     [not found]     ` <20081029.170718.124486817.taka-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2008-10-29  8:29       ` KAMEZAWA Hiroyuki
     [not found]         ` <20081029172918.71995f7a.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-10-29  9:02           ` Balbir Singh [this message]
     [not found]             ` <490826A5.2050003-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-10-29  9:32               ` KAMEZAWA Hiroyuki
     [not found]                 ` <20081029183207.8ae518e1.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-10-30  2:29                   ` Hirokazu Takahashi
2008-10-29  8:36       ` Gui Jianfeng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=490826A5.2050003@linux.vnet.ibm.com \
    --to=balbir-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox