From: Marcel Holtmann <marcel@holtmann.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-efi@vger.kernel.org,
Matthew Garrett <matthew.garrett@nebula.com>,
Jeremy Kerr <jk@ozlabs.org>,
Matt Fleming <matt.fleming@intel.com>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: efivarfs and writev() support
Date: Sun, 8 Mar 2015 15:24:09 -0700 [thread overview]
Message-ID: <33E85F72-FCA0-4DF7-B9E1-46D36244FCA3@holtmann.org> (raw)
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.
Regards
Marcel
next reply other threads:[~2015-03-08 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 22:24 Marcel Holtmann [this message]
2015-03-11 13:42 ` efivarfs and writev() support Matt Fleming
2015-03-11 15:12 ` Marcel Holtmann
2015-03-12 6:34 ` Al Viro
2015-03-12 14:58 ` Marcel Holtmann
2015-03-12 17:03 ` Al Viro
2015-03-14 16:33 ` Marcel Holtmann
2015-03-17 15:46 ` Matt Fleming
2015-03-17 16:03 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33E85F72-FCA0-4DF7-B9E1-46D36244FCA3@holtmann.org \
--to=marcel@holtmann.org \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matthew.garrett@nebula.com \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).