From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753693AbbCKNme (ORCPT ); Wed, 11 Mar 2015 09:42:34 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:41281 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753126AbbCKNmb (ORCPT ); Wed, 11 Mar 2015 09:42:31 -0400 Date: Wed, 11 Mar 2015 13:42:26 +0000 From: Matt Fleming To: Marcel Holtmann Cc: Linux Kernel Mailing List , linux-efi@vger.kernel.org, Matthew Garrett , Jeremy Kerr , Matt Fleming , Al Viro Subject: Re: efivarfs and writev() support Message-ID: <20150311134226.GB24174@codeblueprint.co.uk> References: <33E85F72-FCA0-4DF7-B9E1-46D36244FCA3@holtmann.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <33E85F72-FCA0-4DF7-B9E1-46D36244FCA3@holtmann.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 08 Mar, at 03:24:09PM, Marcel Holtmann wrote: > Hi, > > it seems that efivarfs only supports readv(), but when it comes to > writev(), I am getting an error. Is there any reason to not support > vectored write on this filesystem? Especially with the uint32 header > for each file, I think it would make perfect sense to support it. What error are you seeing? I thought that the vfs fell back to a looped write if the file system doesn't support .write_iter()? But yes, we definitely should support writev(). -- Matt Fleming, Intel Open Source Technology Center