linux-kernel - Re: [PATCH 0/2] range-bw : Another I/O scheduling policy of dm-ioband (v1)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 May 2009 09:18:37 -0400
From:	Chris Snook <chris.snook@...il.com>
To:	Dong-Jae Kang <baramsori72@...il.com>
Cc:	Ryo Tsuruta <ryov@...inux.co.jp>, righi.andrea@...il.com,
	menage@...gle.com, balbir@...ux.vnet.ibm.com,
	guijianfeng@...fujitsu.com, kamezawa.hiroyu@...fujitsu.com,
	agk@...rceware.org, akpm@...ux-foundation.org, axboe@...nel.dk,
	chlunde@...g.uio.no, dave@...ux.vnet.ibm.com, dpshah@...gle.com,
	eric.rannaud@...il.com, fernando@....ntt.co.jp, taka@...inux.co.jp,
	lizf@...fujitsu.com, matt@...ehost.com, dradford@...ehost.com,
	ngupta@...gle.com, randy.dunlap@...cle.com, roberto@...it.it,
	s-uchida@...jp.nec.com, subrata@...ux.vnet.ibm.com,
	yoshikawa.takuya@....ntt.co.jp, nauman@...gle.com,
	fchecconi@...il.com, paolo.valente@...more.it,
	containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, corsetproject@...glegroups.com
Subject: Re: [PATCH 0/2] range-bw : Another I/O scheduling policy of dm-ioband 
	(v1)

On Mon, May 4, 2009 at 6:56 AM, Dong-Jae Kang <baramsori72@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/