linux-kernel - Re: [PATCH] blk-cgroup: Lower minimum weight from 100 to 10.

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 8 Mar 2011 10:03:57 -0500
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Jens Axboe <jaxboe@...ionio.com>
Cc:	Justin TerAvest <teravest@...gle.com>,
	"ctalbott@...gle.com" <ctalbott@...gle.com>,
	"guijianfeng@...fujitsu.com" <guijianfeng@...fujitsu.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] blk-cgroup: Lower minimum weight from 100 to 10.

On Tue, Mar 08, 2011 at 03:36:55PM +0100, Jens Axboe wrote:
> On 2011-03-07 23:53, Justin TerAvest wrote:
> > We've found that we still get good, useful isolation at weights this
> > low. I'd like to adjust the minimum so that any other changes can take
> > these values into account.
> 
> Justin, this looks fine to me if Vivek agrees. You did not sign-off on
> the patch though, so I can't apply it yet. Please re-send with the ack
> from Vivek added and your signed-off-by as well.

The primary reason I am fine with wider weight range because there are
many situations where we just don't get effective 10 times service
differentiation for various reasons like workload don't seem to be
active at the service tree at the same time or if we decide to swith
off idling on faster storage etc.

So because of this leaky nature of service differentiation, it might help to
have a wider range of allowed weights.

Thanks
Vivek
--
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/