All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	David Vrabel <david.vrabel@citrix.com>
Cc: Keir Fraser <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>, Xen-devel <xen-devel@lists.xen.org>,
	Frediano Ziglio <frediano.ziglio@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 0/6] [VERY RFC] Migration Stream v2
Date: Tue, 15 Apr 2014 11:38:56 +0100	[thread overview]
Message-ID: <534D0C40.60908@eu.citrix.com> (raw)
In-Reply-To: <21325.2925.579377.798603@mariner.uk.xensource.com>

On 04/15/2014 11:35 AM, Ian Jackson wrote:
> David Vrabel writes ("Re: [Xen-devel] [PATCH 0/6] [VERY RFC] Migration Stream v2"):
>> On 14/04/14 18:49, George Dunlap wrote:
>>> What did you imagine might constitute an "Optional" record?
>>
>> This was something Ian Jackson asked for and it seems like a useful
>> capabilitity to have for future use.  Not sure what it might be used for
>> yet.
>
> Right.
>
> Long experience with protocol design has taught me that protocols
> should almost always have both an extensibility mechanism which is
> ignored by ignorant receivers, and one which causes ignorant receivers
> to abort.
>
> I don't know yet what we might use it for.  However, we should test
> that it works (ie is ignored by) the receiver (or it will be useless).

Yes, this is the main concern.  2 billion record types should be plenty 
for the "required" field, so the 2 billion allocated for "optional" 
shouldn't be a big loss. :-)  The main risk would be if something which 
is, in fact, required for proper operation on the far side is marked 
"optional".  I guess as long as we have an "ignore everything optional" 
test case we should be OK.

  -George

  reply	other threads:[~2014-04-15 10:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 18:28 [PATCH 0/6] [VERY RFC] Migration Stream v2 Andrew Cooper
2014-04-09 18:28 ` [PATCH 1/6] [HACK] tools/libxc: save/restore v2 framework Andrew Cooper
2014-04-09 18:28 ` [PATCH 2/6] tools/libxc: Stream specification and some common code Andrew Cooper
2014-04-09 18:28 ` [PATCH 3/6] tools/libxc: Scripts for inspection/valdiation of legacy and new streams Andrew Cooper
2014-04-09 18:28 ` [PATCH 4/6] tools/libxc: x86 pv common code Andrew Cooper
2014-04-09 18:28 ` [PATCH 5/6] tools/libxc: x86 pv save implementation Andrew Cooper
2014-04-09 18:28 ` [PATCH 6/6] tools/libxc: x86 pv restore implementation Andrew Cooper
2014-04-10 10:42 ` [PATCH 0/6] [VERY RFC] Migration Stream v2 Ian Campbell
2014-04-10 11:21   ` Andrew Cooper
2014-04-10 13:05     ` Frediano Ziglio
2014-04-10 13:49       ` Andrew Cooper
2014-04-14 17:49     ` George Dunlap
2014-04-14 18:06       ` Andrew Cooper
2014-04-14 18:16         ` George Dunlap
2014-04-14 23:43           ` Andrew Cooper
2014-04-14 18:11       ` David Vrabel
2014-04-15  8:30         ` Frediano Ziglio
2014-04-15 10:35         ` Ian Jackson
2014-04-15 10:38           ` George Dunlap [this message]
2014-04-23 13:47 ` Ian Campbell
2014-04-23 14:02   ` Andrew Cooper
2014-04-23 14:13     ` Ian Campbell

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=534D0C40.60908@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=frediano.ziglio@citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --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.