From: Peter Lieven <pl@kamp.de>
To: qemu-block@nongnu.org
Cc: ronniesahlberg@gmail.com, jcody@redhat.com,
qemu-devel@nongnu.org, Peter Lieven <pl@kamp.de>
Subject: [Qemu-devel] [PATCH 0/2] block/nfs: add support for libnfs pagecache
Date: Tue, 17 May 2016 16:11:53 +0200 [thread overview]
Message-ID: <1463494315-12578-1-git-send-email-pl@kamp.de> (raw)
this adds support for the upcoming libnfs cachepage to Qemu.
While at it neglect to use readahead if cache.direct is on.
Peter Lieven (2):
block/nfs: add support for libnfs pagecache
block/nfs: refuse readahead if cache.direct is on
block/nfs.c | 45 +++++++++++++++++++++++++++++++++++++++++----
1 file changed, 41 insertions(+), 4 deletions(-)
--
1.9.1
next reply other threads:[~2016-05-18 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 14:11 Peter Lieven [this message]
2016-05-17 14:11 ` [Qemu-devel] [PATCH 1/2] block/nfs: add support for libnfs pagecache Peter Lieven
2016-05-17 14:11 ` [Qemu-devel] [PATCH 2/2] block/nfs: refuse readahead if cache.direct is on Peter Lieven
2016-05-18 13:28 ` Jeff Cody
2016-05-19 6:03 ` Peter Lieven
2016-05-18 7:45 ` [Qemu-devel] [PATCH 0/2] block/nfs: add support for libnfs pagecache Fam Zheng
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=1463494315-12578-1-git-send-email-pl@kamp.de \
--to=pl@kamp.de \
--cc=jcody@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
/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).