[okl4-developer] Async Message Buffers

[Abi Nourai]

Hi Ryan,

Sessions are supported by the new release, but not enabled by  
default.  Have a look at the SConstruct for your project (e.g.  
projects/iguana/SConstruct) and search for OKL4_FEATURE_PROFILE.

OKL4_FEATURE_PROFILE is a command line option to the build system that  
accepts two values, NORMAL and EXTRA.  It determines which features  
are build into the kernel.  You'll find that neither NORMAL or EXTRA  
builds in support for sessions.  You can modify this by adding  
CONFIG_SESSIONS to the list of features built by EXTRA or simply  
defining your own OKL4_FEATURE_PROFILE (e.g. EXTRA_PLUS_SESSIONS) .

The reason sessions are not support by any of the standard feature  
profiles is because they will soon be depreciated.  You might be  
interested to know that our POSIX support includes an implementation  
for pipe() which I hope you find useful.

Hope this answers your questions,
Regards
Abi

On 11/06/2008, at 2:41 PM, Ryan Heffernan wrote:
>
>
> The reason i was using this was because i was porting old Nicta L4  
> code
> to OKL4 1.5.2, and the old code made heavy use of async message
> buffers.
>
> I am going to start development on the latest OKL4 release and was
> considering making use of sessions and async message buffers. Since  
> OKL
> is moving towards more capability-based protection I assumed that
> sessions may be on their way out, but I wanted to check with you  
> guys if
> a) async message buffers are still supported by the new release, b)
> maybe there is a better way to handle this kind of communication and  
> c)
> if I should avoid sessions altogether since this functionality is
> outdated and will be replaced by something else.