From: Gerd Hoffmann <kraxel@redhat.com>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-api@vger.kernel.org
Cc: aarcange@redhat.com, Gerd Hoffmann <kraxel@redhat.com>
Subject: [PATCH v7 0/5] Add preadv & pwritev system calls.
Date: Mon, 26 Jan 2009 14:26:24 +0100 [thread overview]
Message-ID: <1232976389-13021-1-git-send-email-kraxel@redhat.com> (raw)
Hi folks,
Next round of the preadv & pwritev patch series. The whitespace bugs
should finally be gone now, checkpatch has nothing to complain about.
There is now a git tree with the patches (branch 'preadv'):
git://git.et.redhat.com/kernel-kraxel.git
http://git.et.redhat.com/?p=kernel-kraxel.git;a=shortlog;h=refs/heads/preadv
Plan it so get this into the linux-next once it comes back to life (after
LCA?).
As for userspace bits someone asked for:
Qemu wants use that to handle virtual disk I/O. A patch for qemu can be
found here: http://article.gmane.org/gmane.comp.emulators.qemu/36851
The code can't put into use yet though as the qemu block layer needs
some changes to pass though iovecs to the disk image format driver code.
Note this isn't the first attempt to get preadv support into the kernel,
therefore I expect others (databases?) will quickly use that too.
Also *BSD has this syscall for quite some time, thus there likely is
code using this in the wild already ...
cheers,
Gerd
next reply other threads:[~2009-01-26 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 13:26 Gerd Hoffmann [this message]
2009-01-26 13:26 ` [PATCH v7 1/5] create compat_readv() Gerd Hoffmann
2009-01-26 13:26 ` [PATCH v7 2/5] create compat_writev() Gerd Hoffmann
2009-01-26 13:26 ` [PATCH v7 3/5] Add preadv and pwritev system calls Gerd Hoffmann
2009-01-26 23:42 ` Michael Kerrisk
2009-01-28 15:04 ` Gerd Hoffmann
2009-01-26 13:26 ` [PATCH v7 4/5] MIPS: Add preadv(2) and pwritev(2) syscalls Gerd Hoffmann
2009-01-26 13:26 ` [PATCH v7 5/5] switch compat readv/preadv/writev/pwritev from fget to fget_light Gerd Hoffmann
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=1232976389-13021-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=aarcange@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®