From: Mats Petersson <mats.petersson@citrix.com>
To: hxkhust <hxkhust@126.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: !!!!!help!I wouldn't be able to meet the deadline!(qcow format image file read operation in qemu-img-xen)[updated]
Date: Wed, 19 Dec 2012 16:23:50 +0000 [thread overview]
Message-ID: <50D1EA16.1070005@citrix.com> (raw)
In-Reply-To: <4e6c46ce.cb93.13bb3e8b8fe.Coremail.hxkhust@126.com>
On 19/12/12 16:04, hxkhust wrote:
> >Date: Wed, 19 Dec 2012 15:32:41 +0000
> >From: Mats Petersson <mats.petersson@citrix.com>
> >To: <xen-devel@lists.xen.org>
> >Subject: Re: [Xen-devel] !!!!!help!I wouldn't be able to meet the
> > deadline!(qcow format image file read operation in
> > qemu-img-xen)[updated]
> >Message-ID: <50D1DE19.1080709@citrix.com>
> >Content-Type: text/plain; charset="GB2312"
> >
> >On 19/12/12 15:23, hxkhust wrote:
> >> Or could you tell me how to cache the data which is read from the
> >> backingfile when a qcow image is regarded as a virtual disk in a
> >> running HVM?
> >I take it the above single question is the effect of my previous reply?
> >Why did you have to "hide" that little extra question in the whole
> >previous e-mail?
> >
> ......yse,that is.
> Because previously what point out is a detail question, the reader may be convenient to answear and at least input less words to me, I guess.
You are, I suppose, aware that most members of this list hasn't even
replied to your original email, and most probably thought your re-send
was simply another copy of the same mail - given that there have been
about 100 mails to the list since, it's not inconceivable.
I very nearly missed the tiny difference between your first, second and
third posting.
> And in this way I can get the one that is more maneuverable.
> >Sorry, don't know the answer to your question [I'm guessing, in general,
> >that the Dom0 will do that for you, subject to available space], just
> >pointing out that there is a minor difference between your previous and
> >current mail.
> >
> yean,the difference is minor.I have no time and I'm worry about the problem.
> I have seen that a lot of questions have more that one Re:XXX mails(mails to answer the question),How could they do that?
Not sure what you are trying to say here. It is your task to make it as
easy as possible for us to help you. Please read the links I sent
earlier. It is REALLY going to help you get better help to understand
that if you "ask smart questions" you get good answers. Included in that
is "do not same the same email several times whilst ignoring replies
already given".
>
> >By caching, do you mean "load the entire file into RAM", or "if a read
> >is requested for the same piece of 'disk' multiple times, I want the
> >previous result to be stored and returned".
> >
> I mean the latter one.Could you give me some proposal?
Keep some sort of memory structure that records the previously read
data, along with "where the data came from" [beware that this needs to
be updated/cleared if there is a write]. If you can find a read for the
location on "disk" that you have cached, then you can pretty much return
immediately.
Exactly what other problems you run into, I'm not sure - as I said
earlier, I'm not overly familiar with this code.
--
Mats
> >--
> >Mats
>
>
next prev parent reply other threads:[~2012-12-19 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 16:04 !!!!!help!I wouldn't be able to meet the deadline!(qcow format image file read operation in qemu-img-xen)[updated] hxkhust
2012-12-19 16:23 ` Mats Petersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-19 15:23 hxkhust
2012-12-19 15:32 ` Mats Petersson
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=50D1EA16.1070005@citrix.com \
--to=mats.petersson@citrix.com \
--cc=hxkhust@126.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 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.