From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40303) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZZF54-0005Ug-GV for qemu-devel@nongnu.org; Tue, 08 Sep 2015 05:20:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZZF4z-0005lr-1B for qemu-devel@nongnu.org; Tue, 08 Sep 2015 05:20:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52272) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZZF4y-0005ks-9x for qemu-devel@nongnu.org; Tue, 08 Sep 2015 05:20:40 -0400 Date: Tue, 8 Sep 2015 17:20:35 +0800 From: Fam Zheng Message-ID: <20150908092035.GG24489@ad.nay.redhat.com> References: <1441699228-25767-1-git-send-email-den@openvz.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1441699228-25767-1-git-send-email-den@openvz.org> Subject: Re: [Qemu-devel] [PATCH RFC 0/5] disk deadlines List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Denis V. Lunev" Cc: Kevin Wolf , qemu-devel@nongnu.org, Stefan Hajnoczi , "qemu-block@nongnu.org Raushaniya Maksudova" [Cc'ing qemu-block@nongnu.org] On Tue, 09/08 11:00, Denis V. Lunev wrote: > To avoid such situation this patchset introduces patch per-drive option > "disk-deadlines=on|off" which is unset by default. The general idea sounds very nice. Thanks! Should we allow user configuration on the timeout? If so, the option should be something like "timeout-seconds=0,1,2...". Also I think we could use werror and rerror to control the handling policy (whether to ignore/report/stop on timeout). Fam