From owner-freebsd-arch@FreeBSD.ORG  Sat Nov 15 17:48:30 2014
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@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 778E7C52;
 Sat, 15 Nov 2014 17:48:30 +0000 (UTC)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 646741B8;
 Sat, 15 Nov 2014 17:48:28 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA05434;
 Sat, 15 Nov 2014 19:50:13 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1XphSN-000PF6-TQ; Sat, 15 Nov 2014 19:48:19 +0200
Message-ID: <546791AA.5060204@FreeBSD.org>
Date: Sat, 15 Nov 2014 19:47:22 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Adrian Chadd <adrian@FreeBSD.org>
Subject: Re: suspending threads before devices
References: <201203202037.q2KKbNfK037014@svn.freebsd.org>	<201203211502.14353.jkim@FreeBSD.org>	<4F6AF1CB.80902@FreeBSD.org>	<201203220748.49635.jhb@freebsd.org>	<20120322141436.GC2358@deviant.kiev.zoral.com.ua>	<54666FD5.6080705@FreeBSD.org>	<20141115105819.GJ17068@kib.kiev.ua>	<54676BA6.7000202@FreeBSD.org>
 <CAJ-Vmo=JbMRH0J4jy03sKxeMV-FP7GoE5R--92241rzeMTMo-g@mail.gmail.com>
In-Reply-To: <CAJ-Vmo=JbMRH0J4jy03sKxeMV-FP7GoE5R--92241rzeMTMo-g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: Konstantin Belousov <kostikbel@gmail.com>, Jung-uk Kim <jkim@FreeBSD.org>,
 "freebsd-arch@freebsd.org" <freebsd-arch@FreeBSD.org>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Nov 2014 17:48:30 -0000

On 15/11/2014 18:41, Adrian Chadd wrote:
> [snip]
> 
> Hm, would just creating a suspend kernel thread make it easier?
> 
> Ie, instead of you doing the suspend in the context of the calling
> process, just have it signal to a kernel thread, so the userland
> thread doing the suspend can also be suspended?

I do not see any significant difference between the two approaches.

-- 
Andriy Gapon