From owner-freebsd-current@FreeBSD.ORG  Sun Jan 11 15:43:24 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D2CDF9E9;
 Sun, 11 Jan 2015 15:43:24 +0000 (UTC)
Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8D012F57;
 Sun, 11 Jan 2015 15:43:24 +0000 (UTC)
Received: from laptop015.home.selasky.org
 (cm-176.74.213.204.customer.telag.net [176.74.213.204])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id DDC9C1FE022;
 Sun, 11 Jan 2015 16:43:21 +0100 (CET)
Message-ID: <54B29A49.3080600@selasky.org>
Date: Sun, 11 Jan 2015 16:44:09 +0100
From: Hans Petter Selasky <hps@selasky.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Jason Wolfe <nitroboost@gmail.com>
Subject: Re: [RFC] kern/kern_timeout.c rewrite in progress
References: <54A1B38C.1000709@selasky.org>
 <20150101005613.4f788b0c@nonamehost.local> <54A49CA5.2060801@selasky.org>
 <54A4A002.8010802@selasky.org> <54A53F4F.2000003@selasky.org>
 <54A92ED1.2070906@selasky.org>
 <CAJ-Vmo=tc-hqykhyc5bQW8qd_34PZU6yfGY8wziByA0xnR3ANQ@mail.gmail.com>
 <54A9A71E.70609@selasky.org>
 <CAAAm0r39Sv3TCvwaCiNQ1Y9iBVtY_nb0A_iNOC41bgxqXmt+4w@mail.gmail.com>
In-Reply-To: <CAAAm0r39Sv3TCvwaCiNQ1Y9iBVtY_nb0A_iNOC41bgxqXmt+4w@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Adrian Chadd <adrian@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>,
 "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jan 2015 15:43:24 -0000

On 01/07/15 00:10, Jason Wolfe wrote:
>
> Hans,
>
> We've been running into 'spin lock held too long' panics in the kernel
> idle threads on 10-STABLE over the past 6 months, so I was interested
> to see your work here in the callout code.  I went ahead and brought
> this patch back to a recent 10.1-STABLE base without much issue,
> kern_timeout.c was actually the only piece with some easily resolvable
> rejections.
>
> I've had a box running stable under load with this patch for a few
> days, and 10 more have just been added to the rotation.  Anyway just
> figured you might be interested in the some feedback while the changes
> are reviewed.
>

Hi,

Thank your for testing this patch. Any updates?

--HPS