From: Gui Jianfeng <guijianfeng-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Hirokazu Takahashi <taka-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: About bio-cgroup
Date: Wed, 29 Oct 2008 16:36:56 +0800 [thread overview]
Message-ID: <490820A8.7050404@cn.fujitsu.com> (raw)
In-Reply-To: <20081029.170718.124486817.taka-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
Hi, Hirokazu-san
Hirokazu Takahashi 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.
I see, thanks.
>
>> Thanks a lot.
>>
>> --
>> Regards
>> Gui Jianfeng
>
> Thanks,
> Hirokazu Takahashi.
>
>
>
--
Regards
Gui Jianfeng
prev parent reply other threads:[~2008-10-29 8:36 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
[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 [this message]
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=490820A8.7050404@cn.fujitsu.com \
--to=guijianfeng-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=taka-jCdQPDEk3idL9jVzuh4AOg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.