From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [OSSTEST PATCH [RFC] 0/3] Series short description
Date: Fri, 6 Dec 2013 10:23:32 +0100 [thread overview]
Message-ID: <1386321812.5338.573.camel@Solace> (raw)
In-Reply-To: <21152.47413.593945.703652@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1973 bytes --]
On gio, 2013-12-05 at 17:34 +0000, Ian Jackson wrote:
> Dario Faggioli writes ("Re: [Xen-devel] [OSSTEST PATCH [RFC] 0/3] Series short description"):
> > ... I knew a language called like that existed, but that is mostly it,
> > and while I try to understand that fancy syntax, any pointer to what I
> > should look at to understand how it "already knows how to parallelise
> > operations on multiple hosts" and hence how I'd be able to "make it
> > capable of doing these kind of stepwise operations on multiple guests"?
>
> Tcl itself is just a programming language. It happens to have very
> good support for writing event-continuation-passing-style programs,
> with little code.
>
Yes, that I knew. I've seen it being used for event based simulation,
but I never got to that.
> (I also really like it.)
>
That I suspected. :-P
> In sg-run-job the core of this is done with the spawn-ts and reap-ts
> procedures. Mostly in sg-run-job, these are combined into run-ts,
> which spawns and then immediately reaps.
>
Ok.
> But there is an existing proc per-host-ts which interprets its
> arguments as a specification of a set of hosts, and spawns the script
> on each host and then reaps them again, so that the same script runs
> in parallel on all the hosts.
>
Right, as I said, I felt like that could be the spot. I'll look into it
and try to understand what goes on there (and the how to extend that as
per my needs).
> The tcl.tk website has comprehensive language documentation of course,
> but I would be happy to help/review/etc. Do you like learning new
> languages ... ?
>
I certainly do! :-)
Thanks for the explanation and the pointers.
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-12-06 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 15:09 [OSSTEST PATCH [RFC] 0/3] Series short description Dario Faggioli
2013-12-05 15:09 ` [OSSTEST PATCH [RFC] 1/3] ts-debian-install: support for installing multiple guests Dario Faggioli
2013-12-05 15:10 ` [OSSTEST PATCH [RFC] 2/3] ts-debian-fixup: support " Dario Faggioli
2013-12-05 15:10 ` [OSSTEST PATCH [RFC] 3/3] ts-guest-start, -stop, -destroy: " Dario Faggioli
2013-12-05 15:25 ` [OSSTEST PATCH [RFC] 0/3] Series short description Ian Jackson
2013-12-05 16:17 ` Dario Faggioli
2013-12-05 17:34 ` Ian Jackson
2013-12-06 9:23 ` Dario Faggioli [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=1386321812.5338.573.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.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 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.