mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: KUROSAWA Takahiro <kurosawa@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org, ckrm-tech@lists.sourceforge.net,
	Balbir Singh <balbir@in.ibm.com>
Subject: Re: [ckrm-tech] [PATCH 1/2] add a CPU resource controller
Date: Tue, 14 Feb 2006 07:15:22 +0530	[thread overview]
Message-ID: <20060214014522.GB28942@in.ibm.com> (raw)
In-Reply-To: <20060213235529.CB13674035@sv1.valinux.co.jp>

On Tue, Feb 14, 2006 at 08:55:29AM +0900, KUROSAWA Takahiro wrote:
> Ah, you are right.  LHS is on per-cpu scale.
> I'll apply your patch.

Great! I also feel that "guarantee" can be explained better (in your first 
documentation patch), especially in the context of multi-cpu systems. Initially 
I was confused what guarantee means in SMP.

-- 
Regards,
vatsa

  reply	other threads:[~2006-02-14  1:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2006-02-09  6:11 ` [PATCH 2/2] connect the CPU resource controller to CKRM KUROSAWA Takahiro
2006-02-13 14:39   ` [ckrm-tech] " Srivatsa Vaddagiri
2006-02-13 23:22     ` KUROSAWA Takahiro
     [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
2006-02-14  5:58     ` KUROSAWA Takahiro
2006-02-14  5:27 ` Srivatsa Vaddagiri
     [not found] <88299102B8C1F54BB5C8E47F30B2FBE201E95DB0@inblr-exch1.eu.uis.unisys.com>
2006-02-14  5:57 ` KUROSAWA Takahiro
     [not found] <88299102B8C1F54BB5C8E47F30B2FBE201E95E78@inblr-exch1.eu.uis.unisys.com>
2006-02-14  6:44 ` KUROSAWA Takahiro
2006-02-15  4:47 Suryanarayanan, Rajaram

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=20060214014522.GB28942@in.ibm.com \
    --to=vatsa@in.ibm.com \
    --cc=balbir@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome