From: Ian Campbell <ian.campbell@citrix.com>
To: Vitaly Chernooky <vitalii.chernookyi@globallogic.com>
Cc: "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
"Oleksandr Dmytryshyn" <oleksandr.dmytryshyn@globallogic.com>,
"Ian Jackson" <Ian.Jackson@eu.citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: Guidelines for new PV protocol submission
Date: Mon, 9 Feb 2015 13:15:11 +0000 [thread overview]
Message-ID: <1423487711.4508.3.camel@citrix.com> (raw)
In-Reply-To: <CANZZXhAs1EkioAPLoZTUJ_c44ryjbsikMdpUXZJ+Xz1A9WjsuQ@mail.gmail.com>
On Mon, 2015-02-09 at 13:59 +0200, Vitaly Chernooky wrote:
> Guys, what do you think about using an Interface Description Language
> such as Google Protocol Buffers or something like?
After a bit of googling and reading it seems like Google Protocol
Buffers includes a specific wire encoding, a la ASN.1 or CORBA, whereas
we need to be able to describe existing binary formats.
I haven't evaluated the suitability for new PV protocols, but it seems
like Protocol Buffers are not really intended for shared memory
protocols (rather network transparent ones). Perhaps I'm wrong though, I
just had a quick look.
Ian.
next prev parent reply other threads:[~2015-02-09 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 12:47 Guidelines for new PV protocol submission Roger Pau Monné
2015-01-20 13:20 ` David Vrabel
2015-01-20 13:39 ` Andrew Cooper
2015-01-20 13:48 ` Jan Beulich
2015-01-20 14:00 ` Andrew Cooper
2015-01-20 16:32 ` Jan Beulich
2015-01-20 14:21 ` Ian Jackson
2015-01-20 16:28 ` Ian Campbell
2015-01-20 13:46 ` Jan Beulich
2015-02-05 10:42 ` Ian Campbell
2015-02-09 11:01 ` Roger Pau Monné
2015-02-09 11:11 ` Ian Campbell
2015-02-09 11:59 ` Vitaly Chernooky
2015-02-09 13:15 ` Ian Campbell [this message]
2015-02-09 13:45 ` Vitaly Chernooky
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=1423487711.4508.3.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vitalii.chernookyi@globallogic.com \
--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 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.