On Tue, Aug 08, 2006 at 11:57:18PM -0700, Ulrich Drepper (drepper@redhat.com) wrote:

Evgeniy Polyakov wrote:

quoted

Question with kevents removal from syscall stays open until Ulrich
accepts or declines mapped buffer implementation.

It was my idea in the first place to use the ring buffer.  I'm sure
others had the same idea but that's what I presented.  So, I see no
reason you should delay making this change because of me.

I did it already :)
So I'm waiting for you to decide if it is what you want, or it should be
implemented in a different way.

The only important thing is that we need to get a useful semantics for
fork and exec.  For fork, it must be possible to "dequeue" entries from
the ring buffer in a thread-safe way.  For exec (where a file descriptor
might survive) we likely need a mechanism to mmap the ring buffer only
based on the file descriptor.  I'm not sure about this, though.

Since reading of events from tha mapped ring can be unlimited and they
are supposed to be removed only by syscall (but not copy them), and
syscall itself is thread safe, there should be no problems with fork
case.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

-- 
	Evgeniy Polyakov