From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754100AbYLLUC4 (ORCPT ); Fri, 12 Dec 2008 15:02:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751585AbYLLUCs (ORCPT ); Fri, 12 Dec 2008 15:02:48 -0500 Received: from mx2.redhat.com ([66.187.237.31]:37843 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751093AbYLLUCr (ORCPT ); Fri, 12 Dec 2008 15:02:47 -0500 Message-ID: <4942C357.4060801@redhat.com> Date: Fri, 12 Dec 2008 21:02:31 +0100 From: Gerd Hoffmann User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: Arnd Bergmann CC: Matthew Wilcox , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org Subject: Re: [PATCH v2] Add preadv and pwritev system calls. References: <1229090440-32120-1-git-send-email-kraxel@redhat.com> <20081212152929.GM26095@parisc-linux.org> <200812122047.31405.arnd@arndb.de> In-Reply-To: <200812122047.31405.arnd@arndb.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Arnd Bergmann wrote: > Aside from that, have you considered doing something even more flexible, > like this? > > struct piovec { > void __user *iov_base; > __kernel_size_t iov_len; > __kernel_loff_t pos; > }; > > asmlinkage ssize_t sys_pwritev(unsigned long fd, > const struct piovec __user *vec, > unsigned long vlen); There is little point in doing so because I *really* want the user-visible API being identical to the existing ones in the *BSD family. Anything else is just a PITA for the applications using this. cheers, Gerd