linux-kernel - Re: [PATCH 0/5] IO-less dirty throttling v8

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Aug 2011 17:00:08 -0400
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Wu Fengguang <fengguang.wu@...el.com>
Cc:	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jan Kara <jack@...e.cz>, Christoph Hellwig <hch@....de>,
	Dave Chinner <david@...morbit.com>,
	Greg Thelen <gthelen@...gle.com>,
	Minchan Kim <minchan.kim@...il.com>,
	Andrea Righi <arighi@...eler.com>,
	linux-mm <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] IO-less dirty throttling v8

On Thu, Aug 11, 2011 at 04:42:55PM -0400, Vivek Goyal wrote:

[..]
> So I see following immediate extension of your scheme possible.
> 
> - Inherit ioprio from iocontext and provide buffered write service
>   differentiation for writers.
> 
> - Create a per task buffered write throttling interface and do
>   absolute throttling of task.
> 
> - We can possibly do the idea of throttling group wide buffered
>   writes only control at this layer using this mechanism.

Though personally I like the idea of absolute throttling at page cache
level as it can help a bit with problem of buffered WRITES impacting
the latency of everything else in the system. CFQ helps a lot but
it idles enough that cost of this isolation is very high on faster
storage.

Deadline and noop really do not do much about protection from WRITEs.

So it is not perfect but might prove to be good enough for some use
cases.

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/