From: Kamala Narasimhan <kamala.narasimhan@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [RFC] xl disk configuration handling
Date: Tue, 01 Feb 2011 09:00:35 -0500 [thread overview]
Message-ID: <4D481203.1090507@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1102011102180.7277@kaball-desktop>
>>> do we really need to change the parsing function that much? I
>>> understand there are significant changes but this is a total rewrite.
>>> I am concerned about all the bugs we might find later after the
>>> release...
>>>
>> This is one change I would really like to go with. Not only does it help with
>> the changes we needed, it also gets rid of code duplication. With this change
>> block-attach can rely on the same parsing code (that is once I submit the
>> block-attach changes patch).
>
> It took us several iterations to get the parsing right, I would like to
> keep the state machine and the field parsing as it is, but each case
> could have its own function to implement it. In other words, would you
> be OK with calling parse_disk_attrib, parse_disk_vdev_info and
> parse_disk_pdev_info from the main switch under DSTATE_PHYSPATH,
> DSTATE_VIRTPATH, etc?
Sure, I will go with appropriate DSTATE_* for each chunk we parse.
Kamala
prev parent reply other threads:[~2011-02-01 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 17:46 [RFC] xl disk configuration handling Kamala Narasimhan
2011-01-31 17:18 ` Stefano Stabellini
2011-01-31 19:25 ` Ian Campbell
2011-01-31 20:39 ` Kamala Narasimhan
2011-01-31 20:19 ` Kamala Narasimhan
2011-02-01 11:13 ` Stefano Stabellini
2011-02-01 14:00 ` Kamala Narasimhan [this message]
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=4D481203.1090507@gmail.com \
--to=kamala.narasimhan@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).