From: jvrao <jvrao@linux.vnet.ibm.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
kvm-devel <kvm@vger.kernel.org>, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org,
Javier Guerra Giraldez <javier@guerrag.com>,
Cam Macdonell <cam@cs.ualberta.ca>
Subject: Re: [Qemu-devel] [GSoC 2010] Pass-through filesystem support.
Date: Tue, 20 Apr 2010 23:33:25 -0700 [thread overview]
Message-ID: <4BCE9C35.1030500@linux.vnet.ibm.com> (raw)
In-Reply-To: <y2s52d4a3891004202120p46f463d2ke15be4c45cbcad70@mail.gmail.com>
Mohammed Gamal wrote:
> On Tue, Apr 20, 2010 at 8:36 PM, jvrao <jvrao@linux.vnet.ibm.com> wrote:
>
> ... <snip> ...
>
>>> This'd be something interesting to do. I wonder if that would fit in
>>> the GSoC timeframe, or whether it'd be a little too short. So how long
>>> you'd estimate something like that would take?
>> I think it would take ~3PM for someone with decent VFS/NFS knowledge.
>> They key is fh-to-dentry mapping. In the loose cache mode client caches
>> this information .. but even in this mode we can't assume that it will be cached
>> forever. Need protocol amendments, client/server side changes to implement
>> this in the no-cache mode which can be used even in the loose cache mode when
>> we get a cache-miss.
>>
>> Thanks,
>> JV
>
> I think I'd be glad to go for virtio-9p in GSoC. The roadmap is a
> little bit hazy for me at the moment but I think we can set the goals.
> I'd appreciate some pointers as to where to get more info on what to
> do and if there is any relevant documentation on that matter.
You can wet your feet by starting with the patch set
"[Qemu-devel] [PATCH -V5 00/21] virtio-9p: paravirtual file system passthrough" on the mailing list.
Start QEMU on any latest distro like Fedora 12; choose mainline kernel for guest.
You can start QEMU with something like "-virtfs local,path=/tmp/,mount_tag=v_tmp"
and mount it on the guest. ex: mount -t 9p -o trans=virtio -o debug=0xFFFF v_tmp /mnt.
http://plan9.bell-labs.com/wiki/plan9/9p2010/index.html gives basic information on .L protocol.
You can start to play around.. by exporting NFS on top of VirtFS..
Thanks,
JV
>
> Regards,
> Mohammed
>
>
next prev parent reply other threads:[~2010-04-21 6:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 16:01 [GSoC 2010] Pass-through filesystem support Mohammed Gamal
2010-04-08 16:02 ` Mohammed Gamal
2010-04-08 16:23 ` Stefan Hajnoczi
2010-04-09 13:18 ` [Qemu-devel] " Luiz Capitulino
2010-04-09 17:11 ` jvrao
2010-04-09 17:23 ` Mohammed Gamal
2010-04-09 21:22 ` Jamie Lokier
2010-04-09 22:17 ` Mohammed Gamal
2010-04-09 22:22 ` Javier Guerra Giraldez
2010-04-09 22:34 ` Mohammed Gamal
2010-04-10 12:12 ` Jamie Lokier
2010-04-10 12:42 ` Mohammed Gamal
2010-04-11 0:35 ` Javier Guerra Giraldez
2010-04-11 22:29 ` Jamie Lokier
2010-04-12 8:15 ` Mohammed Gamal
2010-04-12 8:59 ` Alexander Graf
2010-04-12 12:04 ` Jamie Lokier
2010-04-12 12:10 ` Alexander Graf
2010-04-12 11:58 ` Jamie Lokier
2010-04-12 12:14 ` Alexander Graf
2010-04-12 15:43 ` jvrao
2010-04-13 19:08 ` jvrao
2010-04-13 20:17 ` Mohammed Gamal
2010-04-19 22:54 ` jvrao
2010-04-20 4:26 ` Mohammed Gamal
2010-04-20 18:36 ` [Qemu-devel] " jvrao
2010-04-21 4:20 ` Mohammed Gamal
2010-04-21 6:33 ` jvrao [this message]
2010-04-12 15:16 ` jvrao
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=4BCE9C35.1030500@linux.vnet.ibm.com \
--to=jvrao@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=cam@cs.ualberta.ca \
--cc=javier@guerrag.com \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.com \
--cc=qemu-devel@nongnu.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