From: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
To: Nicholas Rosbrook <rosbrookn@ainfosec.com>
Cc: Brendan Kerrigan <kerriganb@ainfosec.com>,
"wl@xen.org" <wl@xen.org>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Nicolas Belouin <nicolas.belouin@gandi.net>,
"anthony.perard@citrix.com" <anthony.perard@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [RFC] Generating Go bindings for libxl
Date: Tue, 30 Jul 2019 07:48:13 -0600 [thread overview]
Message-ID: <CABfawhmhPy-BWwRfZ-+pB1Zr98ony9jeXoOEOx+HZBm_z+Ez=g@mail.gmail.com> (raw)
In-Reply-To: <5c6f3ed7b2f444918feea4f4b7cec107@ainfosec.com>
On Tue, Jul 30, 2019 at 7:32 AM Nicholas Rosbrook
<rosbrookn@ainfosec.com> wrote:
>
> Hello,
>
> As a follow up to the presentation that Brendan Kerrigan and I gave at Xen
> summit earlier this month, "Client Virtualization Toolstack in Go", I would like to open
> a discussion around the development of Go bindings for libxl. George Dunlap,
> Nicolas Belouin and I have had some discussion off-line already.
>
> So far, these are the topics of discussion:
Hi Nicholas,
to add to the list of topics I just want to mention that perhaps it
may be beneficial to consider parts of the go bindings not go to libxl
at all. I have been digging through libxl for the past couple months
and it's asynchronous callback system is damn near impossible to
follow and I just can't shake the feeling that it would be a lot
easier to follow if it was in go. Not to mention the performance
issues with the built-in garbage collector and fork/exec parts. I'm
also interested only in a very small subset of what libxl does today
but I want to be able to that as fast as possible - domain creation -
which has many steps that could be done in parallel to speed it up..
and that would just be a natural thing to do in go.
Tamas
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-07-30 13:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 13:11 [Xen-devel] [RFC] Generating Go bindings for libxl Nicholas Rosbrook
2019-07-30 13:48 ` Tamas K Lengyel [this message]
2019-07-30 15:49 ` George Dunlap
2019-07-30 18:39 ` Tamas K Lengyel
2019-07-31 15:14 ` George Dunlap
2019-07-30 15:22 ` George Dunlap
2019-07-30 21:52 ` Nicholas Rosbrook
2019-07-31 15:06 ` George Dunlap
2019-07-31 21:22 ` Nicholas Rosbrook
2019-08-01 18:59 ` Nicholas Rosbrook
2019-08-02 15:38 ` George Dunlap
2019-08-02 19:09 ` Nicholas Rosbrook
2019-09-04 0:36 ` Nicholas Rosbrook
2019-09-04 16:52 ` George Dunlap
2019-09-04 16:59 ` George Dunlap
2019-09-04 18:23 ` Nicholas Rosbrook
2019-09-11 20:25 ` Nicholas Rosbrook
2019-09-12 14:37 ` George Dunlap
2019-09-12 17:35 ` Nicholas Rosbrook
2019-09-13 11:21 ` George Dunlap
2019-09-13 13:28 ` Nicholas Rosbrook
2019-09-24 0:33 ` Nicholas Rosbrook
2019-09-30 14:51 ` George Dunlap
2019-09-30 18:08 ` Nicholas Rosbrook
2019-09-04 18:15 ` Nicholas Rosbrook
2019-08-02 15:55 ` George Dunlap
2019-07-30 16:27 ` George Dunlap
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='CABfawhmhPy-BWwRfZ-+pB1Zr98ony9jeXoOEOx+HZBm_z+Ez=g@mail.gmail.com' \
--to=tamas.k.lengyel@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=kerriganb@ainfosec.com \
--cc=nicolas.belouin@gandi.net \
--cc=rosbrookn@ainfosec.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).