From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from bombadil.infradead.org ([65.50.211.133]:45470 "EHLO
        bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751072AbdBTJX1 (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Mon, 20 Feb 2017 04:23:27 -0500
Date: Mon, 20 Feb 2017 01:23:26 -0800
From: Christoph Hellwig <hch@infradead.org>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: linux-fsdevel@vger.kernel.org, jack@suse.cz,
        Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH 1/7] nonblocking aio: Introduce IOCB_FLAG_NONBLOCKING
Message-ID: <20170220092326.GD5664@infradead.org>
References: <20170214024603.9563-1-rgoldwyn@suse.de>
 <20170214024603.9563-2-rgoldwyn@suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170214024603.9563-2-rgoldwyn@suse.de>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Mon, Feb 13, 2017 at 08:45:57PM -0600, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
> 
> This flag informs kernel to bail out if an AIO request will block
> for reasons such as file allocations, or a writeback triggered
> by direct I/O.
> 
> IOCB_FLAG_NONBLOCKING is translated to IOCB_NONBLOCKING for
> iocb->ki_flags.

Back when we did the rwf non0-blocking flag there were some comments
that blocking has a specific meaning in unix, in that we can use poll
or select to wait for it.  Maybe this should have a different name
like NOWAIT?