[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4564E2AB.1020202@redhat.com>
Date: Wed, 22 Nov 2006 15:52:11 -0800
From: Ulrich Drepper <drepper@...hat.com>
To: Evgeniy Polyakov <johnpol@....mipt.ru>
CC: David Miller <davem@...emloft.net>, Andrew Morton <akpm@...l.org>,
netdev <netdev@...r.kernel.org>,
Zach Brown <zach.brown@...cle.com>,
Christoph Hellwig <hch@...radead.org>,
Chase Venters <chase.venters@...entec.com>,
Johann Borck <johann.borck@...sedata.com>,
linux-kernel@...r.kernel.org, Jeff Garzik <jeff@...zik.org>
Subject: Re: [take25 1/6] kevent: Description.
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.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists