Re: mirage + ocaml4

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

Ah yes. ocaml-dns needs a bit of attention anyway, as it now uses Cryptokit 
(thanks to Haris' DNSSEC work).  This pulls in a small set of C bindings that 
need to be made available under Mirage-platform.

I'll leave the ipv4 types in cstruct for the moment under the network stack 
port is done, and then we can tidy it up before release. It's just moving code 
around, so it won't take too long I think.

-a


On 12 Dec 2012, at 11:37, Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx> 
wrote:

> convenience - i think the other place they were defined was ocaml-re which 
> meant pulling in that lib just to get ipv[46] addresses, probably 
> particularly for ocaml-dns which was one of the earlier network libs to be 
> pulled out of the monolithic tree.
> 
> (istr a discussion at the time about pulling the network stack apart more 
> generally so that one might include rather more selectively things like 
> address types. but it was pushed down the stack so to speak :)
> 
> On 12 Dec 2012, at 11:34, Anil Madhavapeddy wrote:
> 
>> I've merged Thomas' cstruct branch and pushed to my working copy at 
>> http://github.com/avsm/ocaml-cstruct.
>> Encouragingly, porting ocaml-xenstore only took a 4 line diff so this should 
>> go pretty fast.
>> 
>> One performance crime that I noticed is the Cstruct.blit_string function, 
>> which does a byte-by-byte copy from a string to a Bigarray.  Pierre, do you 
>> have any thoughts on how to improve this?  A faster blit between them would 
>> be quite useful.
>> 
>> Also Mort, can you remind me why on earth there's a type 'ipv4' and 'ipv6' 
>> in cstruct? This seems very out of place in this library, but was it there 
>> for some dependency reason or just because it's convenient (which is also a 
>> fine answer!).
>> 
>> -anil
> 
> 
> -- 
> Cheers,
> 
> R.
> 
> 
> 
> 
> This message and any attachment are intended solely for the addressee and may 
> contain confidential information. If you have received this message in error, 
> please send it back to me, and immediately delete it.   Please do not use, 
> copy or disclose the information contained in this message or in any 
> attachment.  Any views or opinions expressed by the author of this email do 
> not necessarily reflect the views of the University of Nottingham.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.
>