From: "Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: linux-mm@kvack.org
Subject: [LSF/MM TOPIC] Avoid cache duplication in virtual/paravirtual filesystems
Date: Tue, 08 Feb 2011 20:30:20 -0800 [thread overview]
Message-ID: <4D52185C.7080405@linux.vnet.ibm.com> (raw)
I would like to propose a discussion on VirtFS, a 9P based paravirtual
filesystem for KVM.
Discuss unique advantages and issues with the paravirtual filesystems
I would like to discuss and get community feedback and ideas on how can we avoid
cache
duplication(data and metadata) between host and guests.?
Given that both server (host) and client (guest) is running on the same hardware
we should
be able to avoid double caching of both(host and guest) filesystems.
For details about VirtFS, please see my OLS paper
http://www.sciweavers.org/publications/virtfs-virtualization-aware-file-system-pass-through
Thanks
Venkateswararao Jujjuri (JV)
VirtFS - KVM
LTC, IBM.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2011-02-09 4:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D52185C.7080405@linux.vnet.ibm.com \
--to=jvrao@linux.vnet.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).