|| ||"Frederic Rossi (QB/EMC)" <firstname.lastname@example.org>|
|| ||[ANNOUNCE] Supporting asynchronous events in Linux with AEM|
|| ||Wed, 20 Aug 2003 16:49:40 -0400|
I'd like to announce the availability of AEM (async. event mech.). This
project is an attempt to provide a generic and native support for
asynchronous events in the Linux kernel.
See below for an overview of AEM. More information can be found here
Your comments are valuable and I will be pleased to get any feedback from you.
The primary objective of AEM is to provide a native kernel mechanism, which
doesn't make use of other techniques to support the semantic. The reason behind
this is to be able to handle a very huge number of events in a scalable and
Basically, AEM allows an application to register to system events
by supplying user-space event handlers during registration. When an event
occurs in the kernel the corresponding event handler is executed
with the data in parameter.
AEM is a communication mechanism more than a notification mechanism in the
sense the main goal is really to pass information quickly from the kernel to the
user space applications, both ways. This means the data can be modified by event
handlers and be re-interpreted when back into the kernel.
The second goal behind AEM is to provide the atomic execution of user space
handlers directly in reaction to events. Priorities can be associated with events
to give high priority events the possibility to boost their corresponding
processes. As opposed to other styles of event monitoring mechanisms AEM is
working bottom-up, i.e user processes are executed/created by system events.
Generally, we assume that event handlers are short lived executing
quickly in the same execution context as the calling process. But if necessary
an event handler can also be executed inside a new process context permitting its
execution in parallel with the main thread of execution. In this case, processes
are created on the fly.
I'm taking special care to integrate AEM with existing mechanisms providing
similar, although different, functionalities. I want to stress the fact that
the goal of AEM is not to replace what already exist but to provide a
complementary support in Linux.
I'm conscious the current implementation is not perfect and a lot of
work is still to be done. Any suggestion for improvement is welcome.
Specific structures and activation points for events must be present in the
kernel. This is implemented by a patch supplying this basic infrastructure.
The whole implementation is provided by independent kernel modules. One
module supplies the core functionalities while the other modules supply
specific implementations of event handling mechanisms (fetching and
handling of data). Also, definitions of the calling APIs are implemented
This architecture is very flexible. Different implementations can coexist
in the same time. This gives the possibility to stay compatible in
case of a change of API or semantics.
AEM is currently supported on Linux kernels 2.6.0-test1 and 2.4.20.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/