From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [RFC, PATCH] Extensible AIO interface Date: Tue, 02 Oct 2012 12:34:33 -0700 Message-ID: References: <20121001222341.GF26488@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, tytso@google.com, tj@kernel.org, Dave Kleikamp , Zach Brown , Dmitry Monakhov , "Maxim V. Patlasov" , michael.mesnier@intel.com, jeffrey.d.skirvin@intel.com To: Kent Overstreet Return-path: Received: from mga14.intel.com ([143.182.124.37]:6416 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752051Ab2JBTev (ORCPT ); Tue, 2 Oct 2012 15:34:51 -0400 In-Reply-To: <20121001222341.GF26488@google.com> (Kent Overstreet's message of "Mon, 1 Oct 2012 15:23:41 -0700") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Kent Overstreet writes: > So, I and other people keep running into things where we really need to > add an interface to pass some auxiliary... stuff along with a pread() or > pwrite(). How would you enumerate this? How does the application know what the underlying stack supports/need? How is versioning handled? Frankly, in this form it looks more like a special purpose hack than a general facility. -Andi -- ak@linux.intel.com -- Speaking for myself only