[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a36005b50610032334n50e66198rdfef30e4ccf545c8@mail.gmail.com>
Date: Tue, 3 Oct 2006 23:34:02 -0700
From: "Ulrich Drepper" <drepper@...il.com>
To: "Evgeniy Polyakov" <johnpol@....mipt.ru>
Cc: lkml <linux-kernel@...r.kernel.org>,
"David Miller" <davem@...emloft.net>,
"Ulrich Drepper" <drepper@...hat.com>,
"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>
Subject: Re: [take19 1/4] kevent: Core files.
On 9/20/06, Evgeniy Polyakov <johnpol@....mipt.ru> wrote:
> This patch includes core kevent files:
> [...]
I tried to look at the example programs before and failed. I tried
again. Where can I find up-to-date example code?
Some other points:
- I really would prefer not to rush all this into the upstream kernel.
The main problem is that the ring buffer interface is a shared data
structure. These are always tricky. We need to find the right
combination between size (as small as possible) and supporting all the
interfaces.
- so far only the timer and aio notification is speced out. What
about the rest? Are we sure all aspects can be expressed? I am not
yet.
- we need an interface to add an event from userlevel. I.e., we need
to be able to synthesize events. There are events (like, for instance
the async DNS functionality) which come from userlevel code.
I would very much prefer we look at the other events before setting
the data structures in stone.
-
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