Re: [MirageOS-devel] magpie reference

[Thomas Leonard <talex5@xxxxxxxxx>]

On 14 October 2014 16:48, Richard Mortier
<Richard.Mortier@xxxxxxxxxxxxxxxx> wrote:
> from call:
>
> http://www.cs.nott.ac.uk/~rmm/papers/pdf/osdi04-magpie.pdf
>
> http://dl.acm.org/citation.cfm?id=1251272

Thanks for the reference. Being able to highlight all threads related
to a particular input event could be useful, indeed. In the current
system, we can see that e.g. the blkfront.poll thread gets woken up
for each read response and notifies the main thread waiting for the
data:

http://test.roscidus.com/static/html_viewer.html?t_min=8249.586333&t_max=8249.588562

But we don't link it back to the original request. In this case just
marking the request on the diagram would make it obvious what's
happening, but in more complicated cases some visual indication of the
original source could be useful.

You could probably do your clustering analysis on these traces if you
wanted to. Instrumenting Lwt gets you a lot of information
automatically that you would otherwise have to write schemas for, but
you do still need to handle the multiplexing problem.


-- 
Dr Thomas Leonard        http://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel