From: Linda <lindaj@jma3.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xen.org
Subject: Re: 9p file system for xen
Date: Mon, 16 Nov 2015 20:02:35 -0700 [thread overview]
Message-ID: <564A98CB.9090506@jma3.com> (raw)
In-Reply-To: <20151116173559.GC25764@citrix.com>
Hi Wei,
On 11/16/2015 10:35 AM, Wei Liu wrote:
> On Mon, Nov 16, 2015 at 10:22:41AM -0700, Linda wrote:
...
>>
>> The bug is a timing issue: During virtio's probe step, on the front end, it
>> initialized the mount path. Since at that time, the front end doesn't have
>> access to the back end's entries in xenstore (AFIACT), I either need to put
>> it in xenstore prior to starting, or move the access to this information to
>> later in the initialization.
>>
>> Note, I used the past tense on what virtio did, as of last summer: when I
>> looked at it last week, it appears to have changed since I first used it as
>> a template. I need to investigate this further.
>>
> OK.
>
>> Finally, I've made no provision for how to mount more than one file system
>> for the same guest. This is a feature that virtio provides for in the
>> front-end code (as do I), but I am unclear about how this works in the
>> back-end or at the user level. This is what I suspect will be different in
>> xen, and I'd like some input on what it should look like.
> I think this comes down to how your design the xenstore protocol to
> represent different mount points.
And just reading this gave me the answer I need.
>
>>> The code freeze for next release is going to be end of March next year.
>>> As software engineer often overestimates the progress he or she can
>>> make, I would say we shall aim for getting something working as soon as
>>> possible. Get the design straight and something clean by the end of this
>>> year would be good.
>> Sounds good to me. I'm happy to keep working on this. I just didn't want
>> to find myself in a position where I needed to pass this on to someone else,
>> but I didn't give that person enough time to finish what I'd done.
> Depending on the situation, I can take over the code. You've done enough
> for this project and we don't really want you to work on it for free --
> we don't have provision for more funding at the moment.
Understood.
> If we end up taking over the project, we will still attribute the
> initial implementation to you.
Thanks. Julien said essentially the same thing. Right now, I'm
working on average, less than 10 hours/week, so it's enough to keep my
mind engaged, but it doesn't interfere with anything else.
I will be working for pay, in some capacity (TBD), after the first
of the year. Right now, I'm working to line things up.
Unless something changes drastically, I'll continue to work on this
until the end of the year. I'll start by cleaning things up, and keep
it that way, so no matter what happens, you, or Julien, can take it over.
Linda
>
> Wei.
>
next prev parent reply other threads:[~2015-11-17 3:02 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 [this message]
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
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=564A98CB.9090506@jma3.com \
--to=lindaj@jma3.com \
--cc=julien.grall@citrix.com \
--cc=wei.liu2@citrix.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 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).