From: Wei Liu <wei.liu2@citrix.com>
To: Linda <lindaj@jma3.com>
Cc: Julien Grall <julien.grall@citrix.com>,
Neil Sikka <neilsikka@gmail.com>, Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: 9p file system for xen
Date: Tue, 1 Dec 2015 14:46:48 +0000 [thread overview]
Message-ID: <20151201144648.GV21588@citrix.com> (raw)
In-Reply-To: <565DB0B7.9060505@jma3.com>
On Tue, Dec 01, 2015 at 07:37:43AM -0700, Linda wrote:
>
>
> On 12/1/2015 4:47 AM, Wei Liu wrote:
> >On Mon, Nov 30, 2015 at 12:19:18PM -0500, Neil Sikka wrote:
> >>Hi Wei, could you please explain why/how you would have done the project
> >>differently now and why these patches are not "good"? From my conversation
> >>with Linda, I understood that her code is "Independent of virtio except the
> >>9pvirtio specific code, which is used extensively."
> >>
> >I need to implement a xen transport for 9pfs. Linda was essentially
> >doing the same. But she didn't specify the canonical protocol between
> >frontend and backend.
> For my own edification: In the interests of the limited time of my
> internship, we decided I shouldn't do the initialization using the xen
> toolstack. Were there are other expediencies that I'm unaware of?
>
It's not about toolstack. Toolstack merely sets up xenstore nodes
according to the protocol.
> I tried to follow the xen handshaking protocol between front and back end at
> startup.
>
Yes, that's the right direction. Following existing convention is good
enough for an intern project. Specifying the protocol in detailed is not
the requirement for a prototype.
But in the end to upstream xen-9pfs a canonical protocol is required. A
blessed version of protocol needs to be committed to xen.git tree. We
have a bunch of those in xen.git/xen/include/public/io/ directory.
Wei.
> Thanks.
>
> Linda
> >
> >As for "9pvirtio specific code", I think there is misunderstanding
> >because though a lot of files in QEMU are prefixed with virtio they are
> >actually not specific to virtio at all. I think the "independent of
> >virtio ..." part was referring to the new transport she wrote.
> >
> >Wei.
> >
>
next prev parent reply other threads:[~2015-12-01 14:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 17:23 9p file system for xen Linda
2015-11-16 15:16 ` Wei Liu
2015-11-16 16:36 ` Linda
2015-11-16 16:51 ` Wei Liu
2015-11-16 17:22 ` Linda
2015-11-16 17:35 ` Wei Liu
2015-11-17 3:02 ` Linda
2015-11-17 18:35 ` Neil Sikka
2015-11-17 19:50 ` Linda
2015-11-18 9:56 ` Wei Liu
2015-11-19 14:55 ` Neil Sikka
2015-11-19 15:03 ` Wei Liu
2015-11-19 16:23 ` Linda
2015-11-23 15:51 ` Neil Sikka
2015-11-23 16:05 ` Wei Liu
2015-11-30 17:19 ` Neil Sikka
2015-12-01 11:47 ` Wei Liu
2015-12-01 14:37 ` Linda
2015-12-01 14:46 ` Wei Liu [this message]
2015-12-01 15:27 ` Linda
2015-12-02 17:40 ` Linda
2015-11-19 15:05 ` Wei Liu
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=20151201144648.GV21588@citrix.com \
--to=wei.liu2@citrix.com \
--cc=julien.grall@citrix.com \
--cc=lindaj@jma3.com \
--cc=neilsikka@gmail.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.