OSDev.org

cxzuk wrote: From your example, The string length should be known before it hits the IPC.

Yeah, and this is one thing I like to optimize (and make my life easier ), so that I don´t need to create a new buffer.

cxzuk wrote: I would also like to add that you mention about the producer "giving up its timeslice". This is handled by the scheduler (normally), So how are you going to let the kernel know about the state of ur ringbuffers?

Altough the most part of my ringbuffer will be in userspace, the data who is the reader (and how big the ringbuffer is and things like that) will be in kernelspace and so I only have to make a syscall to wakeup (and maybe boost) the reader.

cxzuk wrote: and also the wiki has some good stuff already on this. http://wiki.osdev.org/Eleanore_Semaphore
http://wiki.osdev.org/Message_Passing

I will have a look at this.