mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Snook <chris.snook@gmail.com>
To: Dong-Jae Kang <baramsori72@gmail.com>
Cc: Ryo Tsuruta <ryov@valinux.co.jp>,
	righi.andrea@gmail.com, menage@google.com,
	balbir@linux.vnet.ibm.com, guijianfeng@cn.fujitsu.com,
	kamezawa.hiroyu@jp.fujitsu.com, agk@sourceware.org,
	akpm@linux-foundation.org, axboe@kernel.dk, chlunde@ping.uio.no,
	dave@linux.vnet.ibm.com, dpshah@google.com,
	eric.rannaud@gmail.com, fernando@oss.ntt.co.jp,
	taka@valinux.co.jp, lizf@cn.fujitsu.com, matt@bluehost.com,
	dradford@bluehost.com, ngupta@google.com,
	randy.dunlap@oracle.com, roberto@unbit.it,
	s-uchida@ap.jp.nec.com, subrata@linux.vnet.ibm.com,
	yoshikawa.takuya@oss.ntt.co.jp, nauman@google.com,
	fchecconi@gmail.com, paolo.valente@unimore.it,
	containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, corsetproject@googlegroups.com
Subject: Re: [PATCH 0/2] range-bw : Another I/O scheduling policy of dm-ioband  (v1)
Date: Mon, 4 May 2009 09:18:37 -0400	[thread overview]
Message-ID: <13a12eea0905040618u7fc48755hdbc3ea6d87c4d68c@mail.gmail.com> (raw)
In-Reply-To: <2891419e0905040356x53643144of77eeaa8c210dce7@mail.gmail.com>

On Mon, May 4, 2009 at 6:56 AM, Dong-Jae Kang <baramsori72@gmail.com> wrote:
> range-bw has two kinds of operation modes, min-max and max mode.
> Min-max mode is to supports guaranteeing the minimum I/O requirement
> and limitation of unnecessary I/O bandwidth at the same time. And max
> mode is to support only limitation. So in case of min-max mode, you
> need to configure min-bw and max-bw values and in case of max mode,
> configure only max-bw.

Please forgive me if I missed a previous discussion, but how is max
mode different from min-max mode with a minimum of zero?  I understand
that there may be some special-case optimizations you can do
internally, but it's unclear to me why you need two different
interfaces.

-- Chris

  reply	other threads:[~2009-05-04 13:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 10:56 Dong-Jae Kang
2009-05-04 13:18 ` Chris Snook [this message]
2009-05-06  1:26   ` Dong-Jae Kang

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=13a12eea0905040618u7fc48755hdbc3ea6d87c4d68c@mail.gmail.com \
    --to=chris.snook@gmail.com \
    --cc=agk@sourceware.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=baramsori72@gmail.com \
    --cc=chlunde@ping.uio.no \
    --cc=containers@lists.linux-foundation.org \
    --cc=corsetproject@googlegroups.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=dpshah@google.com \
    --cc=dradford@bluehost.com \
    --cc=eric.rannaud@gmail.com \
    --cc=fchecconi@gmail.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=guijianfeng@cn.fujitsu.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=matt@bluehost.com \
    --cc=menage@google.com \
    --cc=nauman@google.com \
    --cc=ngupta@google.com \
    --cc=paolo.valente@unimore.it \
    --cc=randy.dunlap@oracle.com \
    --cc=righi.andrea@gmail.com \
    --cc=roberto@unbit.it \
    --cc=ryov@valinux.co.jp \
    --cc=s-uchida@ap.jp.nec.com \
    --cc=subrata@linux.vnet.ibm.com \
    --cc=taka@valinux.co.jp \
    --cc=yoshikawa.takuya@oss.ntt.co.jp \
    /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

all inboxes | Powered by JetHome®