From owner-freebsd-hackers@FreeBSD.ORG  Thu Nov 21 20:18:09 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 79DA77C8;
 Thu, 21 Nov 2013 20:18:09 +0000 (UTC)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com
 [IPv6:2607:f8b0:400d:c00::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1C4242259;
 Thu, 21 Nov 2013 20:18:09 +0000 (UTC)
Received: by mail-qa0-f54.google.com with SMTP id f11so4401168qae.13
 for <multiple recipients>; Thu, 21 Nov 2013 12:18:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=ktYvXsMjnzS6RttthW0sWR+ZnBMCGo/gnxADDTbXmD8=;
 b=ufBv5B7fbLvrtXIJYMWtEAQpIFkB3iRU3CwH3CU6RqlecnLGqN8SX1r04j4RhHyoLE
 8hlaVzBsQGOtbORfVR60NK1d7ydGKdtyiRYHrcPBk7GiTICvx14Y93+pHZpiJA5s4k2K
 BdcaE/fPV4VVNOl7lhP5Zkns7EEWiTtW2V5cz/Zp0Siws46EOQKFOQ7d6iacQXPpCewQ
 7Wx3yI8VCrpujWJawc671Zq4NeeutbAHDRU+uhHuF/TV/2QMwUUhC5v5tqCOqp/oksf1
 4l+tSjdU8lEsjTtOa5S0tuO5EUxfM5xhgi3qcwEHc97oH7Ua763BeWPQv+Io79lvXU+K
 A3dg==
MIME-Version: 1.0
X-Received: by 10.229.13.69 with SMTP id b5mr14764956qca.13.1385065088135;
 Thu, 21 Nov 2013 12:18:08 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.224.207.66 with HTTP; Thu, 21 Nov 2013 12:18:08 -0800 (PST)
In-Reply-To: <201311211414.06849.jhb@freebsd.org>
References: <5287BDB9.10201@FreeBSD.org> <528B7681.6090806@FreeBSD.org>
 <CAJ-Vmon5AuBDO8q3uddSnvqBTq71r9vW66DAk9oVpLKUUbX0mA@mail.gmail.com>
 <201311211414.06849.jhb@freebsd.org>
Date: Thu, 21 Nov 2013 12:18:08 -0800
X-Google-Sender-Auth: HsVRcgu5OF3X7r92FDpzIFeeMoY
Message-ID: <CAJ-VmomHZpJ+XQz6rrZp2W9_4=2zJ53=6x3B79qO-gL4Hjc4dA@mail.gmail.com>
Subject: Re: taskqueue_block
From: Adrian Chadd <adrian@freebsd.org>
To: John Baldwin <jhb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>,
 Andriy Gapon <avg@freebsd.org>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2013 20:18:09 -0000

On 21 November 2013 11:14, John Baldwin <jhb@freebsd.org> wrote:
> On Tuesday, November 19, 2013 10:29:18 pm Adrian Chadd wrote:
>> Yes, and lets fix this. :)
>
> Hmm, is taskqueue_block() always used in context where waiting is safe?

I seem to recall that a taskqueue function may wish to block further
jobs from running. The trouble is that since it was called from a task
queued to that particular taskqueue, it'd hang. Sigh.

So yes, some slightly saner semantics would be nice.


-adrian