From owner-freebsd-questions@freebsd.org  Wed Mar 30 12:23:19 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A44FAE2E90
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Wed, 30 Mar 2016 12:23:19 +0000 (UTC) (envelope-from fidaj@ukr.net)
Received: from frv157.fwdcdn.com (frv157.fwdcdn.com [212.42.77.157])
 (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 1FD7C134B
 for <freebsd-questions@freebsd.org>; Wed, 30 Mar 2016 12:23:18 +0000 (UTC)
 (envelope-from fidaj@ukr.net)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net;
 s=fsm; 
 h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date;
 bh=T7e0xFHRU8kB1XMQn+HKS8FmeWVEMMB+KKnAkj5X8AY=; 
 b=ip7imwzz2TH8F4myF4NVrjRN37Yl+CDutBJd9t2lo3Z86Abah6UJtpCY2Yak4nD6B18MQXQ/DSP1itgorZlQBm7pjAsmgsSY9Irgzdgr/gh2xyrAiDLR7L/mgeTLj09/CdfHrCCfgoWULIYQgxUtX1Quoq2Kkl9oPv1nXUFcDeM=;
Received: from [37.229.193.176] (helo=nonamehost.local)
 by frv157.fwdcdn.com with esmtpsa ID 1alF9G-000Lp2-1Q
 ; Wed, 30 Mar 2016 15:22:58 +0300
Date: Wed, 30 Mar 2016 15:22:57 +0300
From: Ivan Klymenko <fidaj@ukr.net>
To: Rick Miller <vmiller@hostileadmin.com>
Cc: FreeBSD Questions <freebsd-questions@freebsd.org>
Subject: Re: AIO Enabled?
Message-ID: <20160330152257.599d068f@nonamehost.local>
In-Reply-To: <CAHzLAVHx9o5PD45MUhnR28uZrxTGNCqd1eaQ0oqEYR1RaF85QQ@mail.gmail.com>
References: <CAHzLAVHx9o5PD45MUhnR28uZrxTGNCqd1eaQ0oqEYR1RaF85QQ@mail.gmail.com>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Authentication-Result: IP=37.229.193.176; mail.from=fidaj@ukr.net; dkim=pass;
 header.d=ukr.net
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2016 12:23:19 -0000

On Tue, 29 Mar 2016 14:42:57 -0400
Rick Miller <vmiller@hostileadmin.com> wrote:

> Hi all,
> 
> I found old mail threads and blog posts (circa 2006 - 2010) that
> stated AIO is not enabled by default in FreeBSD.  However, when
> running strings on the kernel, it appears AIO bits may be available...
> 
> $ sudo strings -n3 /boot/kernel/kernel | grep -i aio
> aio_swake
> freebsd32_aio_read
> freebsd32_aio_write
> freebsd32_aio_return
> freebsd32_aio_suspend
> freebsd32_aio_cancel
> freebsd32_aio_error
> freebsd32_oaio_read
> freebsd32_oaio_write
> freebsd32_aio_waitcomplete
> freebsd32_aio_fsync
> freebsd32_aio_mlock
> AIOSTOP: bad channel 0x%x
> AIOSYNC chan 0x%03lx pos %lu unimplemented
> AIONWRITE
> AIOGSIZE
> AIOSSIZE
> AIOGFMT
> AIOSFMT
> AIOGMIX
> AIOSMIX
> AIOSTOP
> AIOSYNC
> AIOGCAP
> nfsaio
> aio_prio_delta_max
> aio_max
> aio_listio_max
> 
> aio(4) states it can be linked in the kernel using options VFS_AIO or
> dynamically using loader.conf or kldload suggesting it still is not
> enabled by default.  This brings me to a couple questions I hope are
> easily answered.
> 
> 1) Is AIO still disabled by default in FreeBSD 10.x and newer?
> 2) Does strings send the same output above to STDOUT irregardless of
> whether AIO is enabled/disabled?
> 
> 
> Thanks.
> 

for CURRENT
/usr/src/UPDATING
...
20160301:
        The AIO subsystem is now a standard part of the kernel.  The
        VFS_AIO kernel option and aio.ko kernel module have been removed.
        Due to stability concerns, asynchronous I/O requests are only
        permitted on sockets and raw disks by default.  To enable
        asynchronous I/O requests on all file types, set the
        vfs.aio.enable_unsafe sysctl to a non-zero value.
...