From owner-freebsd-current@FreeBSD.ORG Mon Mar 4 14:15:28 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 09A50103; Mon, 4 Mar 2013 14:15:28 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 749A31AC4; Mon, 4 Mar 2013 14:15:27 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r24EFLuB038772; Mon, 4 Mar 2013 16:15:21 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.0 kib.kiev.ua r24EFLuB038772 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r24EFJ80038709; Mon, 4 Mar 2013 16:15:19 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 4 Mar 2013 16:15:19 +0200 From: Konstantin Belousov To: Poul-Henning Kamp Subject: Re: access to hard drives is "blocked" by writes to a flash drive Message-ID: <20130304141519.GA3794@kib.kiev.ua> References: <201303040712.r247CejP008718@gw.catspoiler.org> <25327.1362404670@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <25327.1362404670@critter.freebsd.dk> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: deeptech71@gmail.com, Don Lewis , freebsd-current@FreeBSD.org, peter@rulingia.com, ian@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2013 14:15:28 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 04, 2013 at 01:44:30PM +0000, Poul-Henning Kamp wrote: > Content-Type: text/plain; charset=3DISO-8859-1 > -------- > In message <201303040712.r247CejP008718@gw.catspoiler.org>, Don Lewis wri= tes: >=20 > >Prior to 231160, the syncer thread would call sync_vnode() for the > >syncer vnode of each mountpoint every 30 seconds [...] >=20 > I agree that the lemming syncer is better, but the fundamental mistake of > only having one syncer thread is probably the root-cause in this case: > One camera-grade flash syncing may take (a lot) more than 30 seconds. >=20 > One mountpoint having trouble (of whatever kind) should not affect > the rest of the mountpoints. >=20 > I'm not sure if the syncer is untangled enough that we can have > per mount-point threads yet, but as soon as we can, we should do that. The problem with "wdrain" is not due to any algorithm in the syncer. I explained it in some details in other mail. --huq684BweRXVnRxX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRNKx2AAoJEJDCuSvBvK1B4kEP/jI/E6OuUPHAKxRxhKgwdqT4 na1z1cFRq0tfznZ6S1SrPREGkwQkBaXgDhdKZcF01cjRcbrgYmF0VTBeS6lUzWUr ibqzHS2USCthRMnH8ENgUxr2ExIx0S0HbwIMzQkt0KQfE/JZsxxraO08iwaOWJTC VJXalPGl9QEJkpRKccl1UPF4KrIZn3T5HbYqA2tGZQiK0UyNmU6xty1EYSG/M3yf A8/JZUpdAwPicDIvRdDniMgu7CX4JLvbFTjr/sfCH9VOThdbaqZZzZz2GuSqn5cq bi9GAkEJd4loeVA+5RAy4RSQwKeZacQQPT+8F+O1Y32NHWdOgKKb8zg+B2qwAnm4 GdPKWYq9lYfUHSimtH5jwMdBUW6wBF8JI9baDQXmUlrjvhLN3jDt/HRm+y1b/Y4k GzbyBCPMygQKj/Axq5RvGUdeGBcRtUwhe6UE89P7CSy4DnLF5YJKTUy59Unf/F0c r2K5vT2BsRyuW0V+hItBjaa2AtwcLMcmy/Jfbf2f/juHTWx3tYdoVypheZ8O3wRn U1T7ohNgueS8JoD+9KEh7/Wz/iH/cei0YSO5V3vRv5g2t+ykEkM5SGyayR4wcs12 1oYMGpq6hl7vReX3WOVMnAtERHaqfK9LE2sg7JNG/3TVyhqj0sqQ+RqpgxzXEC5t QppEiB2V8JVSeanDDNFr =e4gL -----END PGP SIGNATURE----- --huq684BweRXVnRxX--