LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hirokazu Takahashi <taka@valinux.co.jp>
To: yamamoto@valinux.co.jp
Cc: agk@redhat.com, xen-devel@lists.xensource.com,
	containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, dm-devel@redhat.com
Subject: Re: [dm-devel] [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview
Date: Thu, 24 Jan 2008 19:14:56 +0900 (JST)	[thread overview]
Message-ID: <20080124.191456.119427875.taka@valinux.co.jp> (raw)
In-Reply-To: <20080124033807.42D7B1E3C0C@siro.lan>

Hi,

> > > On Wed, Jan 23, 2008 at 09:53:50PM +0900, Ryo Tsuruta wrote:
> > > > Dm-band gives bandwidth to each job according to its weight, 
> > > > which each job can set its own value to.
> > > > At this time, a job is a group of processes with the same pid or pgrp or uid.
> > > 
> > > It seems to rely on 'current' to classify bios and doesn't do it until the map
> > > function is called, possibly in a different process context, so it won't
> > > always identify the original source of the I/O correctly:
> > 
> > Yes, this should be mentioned in the document with the current implementation
> > as you pointed out.
> > 
> > By the way, I think once a memory controller of cgroup is introduced, it will
> > help to track down which cgroup is the original source.
> 
> do you mean to make this a part of the memory subsystem?

I just think if the memory subsystem is in front of us, we don't need to
reinvent the wheel.

But I don't have a concrete image how the interface between dm-band and
the memory subsystem should be designed yet. I'd be appreciate if some of
the cgroup developers give some ideas about it.

Thanks,
Hirokazu Takahashi.


> YAMAMOTO Takashi


  reply	other threads:[~2008-01-24 10:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 12:53 Ryo Tsuruta
2008-01-23 12:56 ` [PATCH 1/2] dm-band: The I/O bandwidth controller: Source code patch Ryo Tsuruta
2008-01-23 13:33   ` Frans Pop
2008-01-23 15:48     ` Ryo Tsuruta
2008-01-27 15:44     ` Frans Pop
2008-01-23 12:58 ` [PATCH 2/2] dm-band: The I/O bandwidth controller: Document Ryo Tsuruta
2008-01-23 19:57   ` Andi Kleen
2008-01-24 10:32     ` Ryo Tsuruta
2008-01-23 14:32 ` [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview Peter Zijlstra
2008-01-23 17:25   ` Ryo Tsuruta
2008-01-23 14:47 ` [dm-devel] " Alasdair G Kergon
2008-01-23 16:21   ` Hirokazu Takahashi
2008-01-24  3:38     ` YAMAMOTO Takashi
2008-01-24 10:14       ` Hirokazu Takahashi [this message]
2008-01-25  6:26         ` YAMAMOTO Takashi
2008-01-25  7:07 ` dm-band: The I/O bandwidth controller: Performance Report Ryo Tsuruta
2008-01-29  6:42   ` [Xen-devel] " INAKOSHI Hiroya
2008-01-30  3:32     ` Ryo Tsuruta

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=20080124.191456.119427875.taka@valinux.co.jp \
    --to=taka@valinux.co.jp \
    --cc=agk@redhat.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=yamamoto@valinux.co.jp \
    --subject='Re: [dm-devel] [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).