linux-kernel - Re: [PATCH 18/20] blkio: arm idle timer even if think time is great then time slice left

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]

Message-ID: <x498wemt8ky.fsf@segfault.boston.devel.redhat.com>
Date:	Wed, 04 Nov 2009 14:04:45 -0500
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	linux-kernel@...r.kernel.org, jens.axboe@...cle.com,
	nauman@...gle.com, dpshah@...gle.com, lizf@...fujitsu.com,
	ryov@...inux.co.jp, fernando@....ntt.co.jp, s-uchida@...jp.nec.com,
	taka@...inux.co.jp, guijianfeng@...fujitsu.com,
	balbir@...ux.vnet.ibm.com, righi.andrea@...il.com,
	m-ikeda@...jp.nec.com, akpm@...ux-foundation.org, riel@...hat.com,
	kamezawa.hiroyu@...fujitsu.com
Subject: Re: [PATCH 18/20] blkio: arm idle timer even if think time is great then time slice left

Vivek Goyal <vgoyal@...hat.com> writes:

> o Now we plan to wait for a queue to get backlogged before we expire it. So
>   we need to arm slice timer even if think time is greater than slice left.
>   if process sends next IO early and time slice is left, we will dispatch it
>   otherwise we will expire the queue and move on to next queue.

Should this be rolled into patch 17?  I'm just worried about breaking
bisection runs.  What happens if this patch isn't applied?

Cheers,
Jeff
--
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/