From owner-freebsd-fs@freebsd.org Fri Dec 29 05:29:00 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4159BEAAF4F; Fri, 29 Dec 2017 05:29:00 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 169BA7CBB6; Fri, 29 Dec 2017 05:28:53 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (115-166-0-128.dyn.iinet.net.au [115.166.0.128]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id vBT5Sl0c007101 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 28 Dec 2017 21:28:50 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: add BIO_NORETRY flag, implement support in ata_da, use in ZFS vdev_geom To: Andriy Gapon , freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org References: <391f2cc7-0036-06ec-b6c9-e56681114eeb@FreeBSD.org> From: Julian Elischer Message-ID: <9512ddbe-f9a1-caa7-10ac-ef87870bf48b@freebsd.org> Date: Fri, 29 Dec 2017 13:28:41 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <391f2cc7-0036-06ec-b6c9-e56681114eeb@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Dec 2017 05:29:00 -0000 On 24/11/17 6:30 pm, Andriy Gapon wrote: > https://reviews.freebsd.org/D13224 > > Anyone interested is welcome to join the review. > Thanks. I see you closed the review. However don't stop working with that problem.. It's still something that a worth a solution, even if not exactly That solution. Maybe a generic idea through the block IO layer of transaction requirements. We did face this issue in a BSD4.3 variant in 1990 where a single disk error would result in a cascading shockwave of slowdowns that took some time to resolve. The issue even comes up in networking too, especially with realtime video where "don't bother, we missed the window" comes into play.