From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [PATCH 2/8] aio: disable retry Date: Mon, 26 Oct 2009 12:00:13 -0400 Message-ID: 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 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:43274 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753105AbZJZQAO (ORCPT ); Mon, 26 Oct 2009 12:00:14 -0400 In-Reply-To: <1256243157-16667-3-git-send-email-zach.brown@oracle.com> (Zach Brown's message of "Thu, 22 Oct 2009 13:25:51 -0700") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Zach Brown writes: > 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. Frankly, the retry-based AIO never made it, and no one has been promoting it for, what, 5 years or more? Let's just get rid of it. Reviewed-by: Jeff Moyer