> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Roland Dreier
> Sent: Tuesday, January 16, 2007 1:11 PM
> To: Tziporet Koren
> Cc: EWG; OPENIB
> Subject: Re: [openib-general] Minutes for January 15, 2007 
> teleconference about OFED 1.2 development progress toward code freeze
> 
>  >    * libibverbs 1.1: (from Roland)
>  >          o Fork support - done

Roland:
        To what extent Fork is supported ? Is this a complete solution
that any style fork() code should work, or do we still need some sync
between parent and child so that  child won't touch pinned page before
call exec() ?

        Thank you.

--CQ


>  >          o Minor ABI extensions for new low-level drivers - done
>  >          o Better low-level driver handling, including 
> multiple drivers
>  >            linked in statically - done
>  >          o Dropped from OFED 1.2:
>  >                + Memory windows
> 
> OK, I was planning on postponing them until libibverbs 1.2.
> 
>  >                + Reregister memory region (incl. extend without
>  >                  unregister...)
> 
> I will include the basic API but no implementation for this 
> so that we have a chance at including it in a future release 
> of libibverbs 1.1 without breaking API or ABI.
> 
>  >                + libibverbs 1.0 to be included as well
> 
> I believe I have a way to make libibverbs 1.1 
> binary-compatible with applications (but not drivers) built 
> against libibverbs 1.0.  So it will probably not be necessary 
> to include libibverbs 1.0.
> 
>  - R.
> 
> _______________________________________________
> openib-general mailing list
> [email protected]
> http://openib.org/mailman/listinfo/openib-general
> 
> To unsubscribe, please visit 
> http://openib.org/mailman/listinfo/openib-general
> 
> 

_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Reply via email to