From owner-freebsd-current@FreeBSD.ORG Sun Jul 31 21:21:20 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E256106567C; Sun, 31 Jul 2011 21:21:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id E92A68FC17; Sun, 31 Jul 2011 21:21:19 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAPzFNU6DaFvO/2dsb2JhbABAhEekDoFAAQEFI1YbDgoCAg0ZAlkGtm6QF4ErhAeBEASSe5EA X-IronPort-AV: E=Sophos;i="4.67,296,1309752000"; d="scan'208";a="132951885" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 31 Jul 2011 17:21:19 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id F282BB3F27; Sun, 31 Jul 2011 17:21:18 -0400 (EDT) Date: Sun, 31 Jul 2011 17:21:18 -0400 (EDT) From: Rick Macklem To: Andriy Gapon Message-ID: <2090844362.1227850.1312147278961.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4E35ACDD.90303@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: FreeBSD-Current Subject: Re: Heavy I/O blocks FreeBSD box for several seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 31 Jul 2011 21:21:20 -0000 Abdriy Gapon wrote: > on 31/07/2011 22:03 Rick Macklem said the following: > > Ok, so if the scheduler spin lock is being held too long, what could > > cause this, if it isn't a scheduler bug? > > > > I can't think of how NFS would affect this beyond causing a heavy > > I/O > > load, but if there is some way it does, I suppose I need to know > > what > > that is? > > I think I've already referred to the thread on stable@. > This is currently being investigated. > > P.S. > Just a pure illustration you can grep for thread_lock to see where > else outside > schedulers the sched locks are taken. > -- Yes, I see what you mean (ie. it's all over the place). Sorry about the noise, rick