From owner-freebsd-arch@FreeBSD.ORG  Fri Nov 23 19:17:13 2012
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id CA5F6805
 for <arch@freebsd.org>; Fri, 23 Nov 2012 19:17:13 +0000 (UTC)
 (envelope-from bright@mu.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
 by mx1.freebsd.org (Postfix) with ESMTP id ACF988FC12
 for <arch@freebsd.org>; Fri, 23 Nov 2012 19:17:13 +0000 (UTC)
Received: from Alfreds-MacBook-Pro-5.local
 (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218])
 by elvis.mu.org (Postfix) with ESMTPSA id 101C81A3D5B;
 Fri, 23 Nov 2012 11:17:07 -0800 (PST)
Message-ID: <50AFCBB3.9060708@mu.org>
Date: Fri, 23 Nov 2012 11:17:07 -0800
From: Alfred Perlstein <bright@mu.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Oleksandr Tymoshenko <gonzo@bluezbox.com>
Subject: Re: [RFC] sema_wait_sig
References: <E5FE70A7-D2D2-4021-950B-48FD84F11F08@bluezbox.com>
In-Reply-To: <E5FE70A7-D2D2-4021-950B-48FD84F11F08@bluezbox.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: arch@freebsd.org
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.14
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: Fri, 23 Nov 2012 19:17:13 -0000

On 11/22/12 10:12 PM, Oleksandr Tymoshenko wrote:
> Hello,
>
> Is there any particular reason FreeBSD does not have sema_wait_sig
> function? It seems to be easily implementable using cv_wait_sig
> function.
>
> The reason I'm asking is that I'm getting some Linux drivers
> ported to FreeBSD and the code in question relies on semaphores
> and there is no obvious alternative to down_interruptible function.
> I realize that not all approaches to driver development are easily
> mappable from OS to OS but in this case lack of cv_wait_sig seems
> like gap in API. Unless of course there is strong rationale behind it.
>
Sounds like just an oversight.  Go for it!

-Alfred