Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759909Ab3DBCgY (ORCPT ); Mon, 1 Apr 2013 22:36:24 -0400 Received: from li9-11.members.linode.com ([67.18.176.11]:58044 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759834Ab3DBCgX (ORCPT ); Mon, 1 Apr 2013 22:36:23 -0400 Date: Mon, 1 Apr 2013 22:36:09 -0400 From: "Theodore Ts'o" To: Kent Overstreet Cc: linux-kernel@vger.kernel.org, linux-aio@kvack.org, akpm@linux-foundation.org, Zach Brown , Felipe Balbi , Greg Kroah-Hartman , Mark Fasheh , Joel Becker , Rusty Russell , Jens Axboe , Asai Thambi S P , Selvan Mani , Sam Bradshaw , Jeff Moyer , Al Viro , Benjamin LaHaise Subject: Re: [PATCH 16/33] aio: use cancellation list lazily Message-ID: <20130402023609.GE30122@thunk.org> Mail-Followup-To: Theodore Ts'o , Kent Overstreet , linux-kernel@vger.kernel.org, linux-aio@kvack.org, akpm@linux-foundation.org, Zach Brown , Felipe Balbi , Greg Kroah-Hartman , Mark Fasheh , Joel Becker , Rusty Russell , Jens Axboe , Asai Thambi S P , Selvan Mani , Sam Bradshaw , Jeff Moyer , Al Viro , Benjamin LaHaise References: <1363883754-27966-1-git-send-email-koverstreet@google.com> <1363883754-27966-17-git-send-email-koverstreet@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1363883754-27966-17-git-send-email-koverstreet@google.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1275 Lines: 29 On Thu, Mar 21, 2013 at 09:35:37AM -0700, Kent Overstreet wrote: > Cancelling kiocbs requires adding them to a per kioctx linked list, which > is one of the few things we need to take the kioctx lock for in the fast > path. But most kiocbs can't be cancelled - so if we just do this lazily, > we can avoid quite a bit of locking overhead. > > While we're at it, instead of using a flag bit switch to using ki_cancel > itself to indicate that a kiocb has been cancelled/completed. This lets > us get rid of ki_flags entirely. Reviewed-by: "Theodore Ts'o" One nit.... > + * And since most things don't implement kiocb cancellation and we'd really like > + * kiocb completion to be lockless when possible, we use ki_cancel to > + * synchronize cancellation and completion - we only set it to KIOCB_CANCELLED > + * with xchg() or cmpxchg(), see batch_complete_aio() and kiocb_cancel(). It's not batch_complete_aio() until later in the patch series.... as of this commit, it's still aio_complete() - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/