[lkml]   [2006]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [take25 1/6] kevent: Description.
On Wed, Nov 22, 2006 at 03:52:11PM -0800, Ulrich Drepper ( wrote:
> Evgeniy Polyakov wrote:
> >+ struct kevent_ring
> >+ {
> >+ unsigned int ring_kidx, ring_uidx, ring_over;
> >+ struct ukevent event[0];
> >+ }
> >+ [...]
> >+ring_uidx - index of the first entry userspace can start reading from
> Do we need this value in the structure? Userlevel cannot and should not
> be able to modify it. So, userland has in any case to track the tail
> pointer itself. Why then have this value at all?
> After kevent_init() the tail pointer is implicitly assumed to be 0.
> Since the front pointer (well index) is also zero nothing is available
> for reading.

uidx is an index, starting from which there are unread entries. It is
updated by userspace when it commits entries, so it is 'consumer'
pointer, while kidx is an index where kernel will put new entries, i.e.
'producer' index. We definitely need them both.
Userspace can only update (implicitly by calling kevent_commit()) uidx.

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

Evgeniy Polyakov
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-11-23 12:59    [W:0.124 / U:4.568 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site