From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: KUROSAWA Takahiro <kurosawa@valinux.co.jp>
Cc: "Suryanarayanan, Rajaram" <Rajaram.Suryanarayanan@in.unisys.com>,
linux-kernel@vger.kernel.org, ckrm-tech@lists.sourceforge.net,
balbir.singh@in.ibm.com
Subject: Re: [ckrm-tech] [PATCH 1/2] add a CPU resource controller
Date: Tue, 14 Feb 2006 11:08:52 +0530 [thread overview]
Message-ID: <20060214053852.GD28942@in.ibm.com> (raw)
In-Reply-To: <20060214052604.7EA9174031@sv1.valinux.co.jp>
On Tue, Feb 14, 2006 at 02:26:04PM +0900, KUROSAWA Takahiro wrote:
> It's not a forward port of the existing CPU resource controller
> but a new CPU resource controller for CKRM. Its resource control
> mechanism is different from that of the existing one.
Hmm ..I guess it depends on which version of CKRM you are referring when
you say "existing". When I replied earlier, I was referring to f-series.
f-series cpu controller is based on the patch you sent to lkml right?
--
Regards,
vatsa
next prev parent reply other threads:[~2006-02-14 5:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <88299102B8C1F54BB5C8E47F30B2FBE201E95CD2@inblr-exch1.eu.uis.unisys.com>
2006-02-14 5:26 ` [ckrm-tech] [PATCH 1/2] add a CPU resource controller KUROSAWA Takahiro
2006-02-14 5:38 ` Srivatsa Vaddagiri [this message]
2006-02-14 5:58 ` KUROSAWA Takahiro
2006-02-14 5:27 ` Srivatsa Vaddagiri
2006-02-15 4:47 Suryanarayanan, Rajaram
[not found] <88299102B8C1F54BB5C8E47F30B2FBE201E95E78@inblr-exch1.eu.uis.unisys.com>
2006-02-14 6:44 ` KUROSAWA Takahiro
[not found] <88299102B8C1F54BB5C8E47F30B2FBE201E95DB0@inblr-exch1.eu.uis.unisys.com>
2006-02-14 5:57 ` KUROSAWA Takahiro
-- strict thread matches above, loose matches on Subject: below --
2006-02-09 6:11 [PATCH 0/2] CKRM " KUROSAWA Takahiro
2006-02-09 6:11 ` [PATCH 1/2] add a " KUROSAWA Takahiro
2006-02-13 14:33 ` [ckrm-tech] " Srivatsa Vaddagiri
2006-02-13 23:55 ` KUROSAWA Takahiro
2006-02-14 1:45 ` Srivatsa Vaddagiri
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=20060214053852.GD28942@in.ibm.com \
--to=vatsa@in.ibm.com \
--cc=Rajaram.Suryanarayanan@in.unisys.com \
--cc=balbir.singh@in.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=kurosawa@valinux.co.jp \
--cc=linux-kernel@vger.kernel.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.