From owner-freebsd-arch@FreeBSD.ORG  Thu Jul 19 00:10:29 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 A9C851065674;
	Thu, 19 Jul 2012 00:10:29 +0000 (UTC)
	(envelope-from listlog2011@gmail.com)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 769838FC12;
	Thu, 19 Jul 2012 00:10:29 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6J0ASFs030941;
	Thu, 19 Jul 2012 00:10:28 GMT (envelope-from listlog2011@gmail.com)
Message-ID: <50075072.5050906@gmail.com>
Date: Thu, 19 Jul 2012 08:10:26 +0800
From: David Xu <listlog2011@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: George Neville-Neil <gnn@FreeBSD.org>
References: <3CE55F29-A5B2-44A7-8854-1ED38BAE6F16@FreeBSD.org>
In-Reply-To: <3CE55F29-A5B2-44A7-8854-1ED38BAE6F16@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: arch@FreeBSD.org
Subject: Re: aio in GENERIC?
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: davidxu@FreeBSD.org
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Thu, 19 Jul 2012 00:10:29 -0000

On 2012/7/18 22:43, George Neville-Neil wrote:
> Howdy,
>
> I was wondering why aio is not yet in GENERIC.  Now that it's properly locked and all.
>
> Best,
> George
>

I think one of the problem in the AIO code is it allows user code to 
pass pipe, socket and other file
handles to  kernel,  however it may not work well, the AIO threads may 
be blocked
forever.  I suggest to disable support for socket or pipe except normal 
file or disk device.
it should either fully support it or do not support it at all, not 
half-baked.

Regards,
David Xu