From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 2/8] aio: disable retry
Date: Sun, 25 Oct 2009 03:37:21 -0400
Message-ID: <20091025073721.GB6965@infradead.org>
References: <1256243157-16667-1-git-send-email-zach.brown@oracle.com> <1256243157-16667-2-git-send-email-zach.brown@oracle.com> <1256243157-16667-3-git-send-email-zach.brown@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org
To: Zach Brown <zach.brown@oracle.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from bombadil.infradead.org ([18.85.46.34]:39565 "EHLO
	bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752744AbZJYHhQ (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Sun, 25 Oct 2009 03:37:16 -0400
Content-Disposition: inline
In-Reply-To: <1256243157-16667-3-git-send-email-zach.brown@oracle.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Thu, Oct 22, 2009 at 01:25:51PM -0700, Zach Brown wrote:
> This patch ensures that aio ops won't be retried.  Code that uses EIOCBRETRY
> will fail to build and modules that reference kick_iocb() won't load.
> 
> This simplifies an upcoming patch by ensuring that it doesn't have to support
> aio ops that retry.  Further patches could remove much more of fs/aio.c if we
> chose to remove retry-based aio support.

Is there any good reason to keep it?