Re: [Xen-devel] Domain Save Image Format proposal (draft B)

[Zoltan Kiss <zoltan.kiss@xxxxxxxxxx>]

On 11/02/14 04:12, Shriram Rajagopalan wrote:
> On Mon, Feb 10, 2014 at 7:35 PM, Andrew Cooper
> >         The marker field can be used to distinguish between legacy
> >         images and
> >         those corresponding to this specification.  Legacy images will
> >         have at
> >         one or more zero bits within the first 8 octets of the image.
> >
> >         Fields within the image header are always in _big-endian_ byte
> >         order,
> >         regardless of the setting of the endianness bit.
> >
> >
> >     and more endian-ness mess.
>     Network order is perfectly valid.  Is is how all your network
>     packets arrive...
>
>
>
>
> True. But why should we explicitly convert the application level data to
> network byte order and then convert it back to host byte order, when its
> already going to be done by the underlying stack, as you put it?
TCP doesn't change the byte order of the payload, only header fields are 
defined to be in big endian, AFAIK.
Zoli

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel