aem-devel Mailing List for AEM - Linux Asynchronous Event Mechanism
Brought to you by:
fjrossi
Menu
▾
▴
aem-devel — AEM development
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(3) |
Mar
(4) |
Apr
(1) |
May
(1) |
Jun
(6) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ashish B. <ash...@fl...> - 2005-06-01 10:21:31
|
Hi; I want to use aem on kernel 2.4.26. I am facing some problems when I am trying to compile the kernel after installing the patch. To install the patch I am using the following command " patch -b --verbose -p1 < "patch available with 2.4.20". Even I have tried this 2.4.20-8 kernel same problem. Please help me out in this regard. Is there any special steps need to follow for kernel compilation regards; Ashish Bhargava *********************** FSS-Private *********************** "DISCLAIMER: This message is proprietary to Flextronics Software Systems Limited (FSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." |
|
From: <ben...@id...> - 2004-05-22 12:04:26
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-06-29 17:53:17
|
-----Original Message----- From: Frederic Rossi (LMC) Sent: Sunday, June 29, 2003 1:40 PM To: 'aem...@li...' Subject: [aem-devel] Please Ignore Testing. Troubles with archives. F. |
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-06-29 17:43:45
|
Testing. Troubles with archives. F. |
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-06-26 01:36:38
|
Ardelle, As I already told you, I really appreciate your help. AEM is a great project to work on because it is new. Also it is more than a notification mech. AEM brings a new software development model into Linux. For that reason there is not much documentation to rely on. Which also means that I want to be very careful regarding what is to be integrated or not. I wi= ll also be very carefull not to integrate new features before the current release is not completly stable or at least free of bad bugs. Otherwise it will become a nightmare to debug. SMP is not a feature. It is really a needed architecture. Some bad bugs c= an make AEM crash or freeze. This is always the case for any software however. The ga= me is to catch them all and correct them. But I want to be clear on that, when = I say AEM needs to be stabilized it doesn't mean it crashes all the time, I mea= n it needs to be stabilized under high stress or for other sporadic cases. This is especially true for SMP. These bugs and pbms are really difficult to correct. Regarding the test case with 0 as a parameter, this is clearly a paramete= r missuse, Alhough the input value is not tested correctly, this is not the problem. The only way to get hands dirty is really to use it a lot. Is it the only test you did ? How much timers are you able to start ? Did you try other examples ? a TCP/IP server for example ? Try to run different configurations and the= n stress them. Frederic ----- Original Message ----- From: "Fan, Ardelle" <ard...@in...> To: "Frederic Rossi (LMC)" <Fre...@er...> Cc: "Hu, Boris" <bor...@in...>; <aem...@li...> Sent: Monday, June 23, 2003 4:46 AM Subject: RE: AEM work Hi Frederic Maybe we were too hurried. We have already downloaded the source code and went through roughly. And now we are setting up the environment and trying all test cases. As for our intention about AEM, to be frankly, we just hope to contribute. We really wish to do some help to AEM project. UP/SMP issue is a good point and we are investigating from test case to reproduce the problem. Could you tell us how did you find that it has this kind of issue? running some test case or ju= st leave it with some days to see it hang (or crash)? We plan to first reproduce it and try to shorten the time before hang happens in order to ease future debugging. How do you think about it? And any suggestion about it? And here is another thing we found in our try: In aem-testsuite-v0.3/Timer_Pkg, when we pass the command "./timer 0", 5 tim= er is created. And then there are several lines of timeout messages showing up the scree= n. After that the linux box(SMP) hung in about ten seconds. I know that 0 is not a valid parameter for the timer interval. I just want to se= e what will happen in such edge condition. Can we take it as the symptom of the UP/SMP issue? In last mail I have asked the TODO list, because SMP issue can be a globa= l and deep hidden bug. Maybe some small feature support can be some threads for us to get hands dirty. If you think there isn't any available for us, just forget about it. Thank you Regards/Ardelle -----Original Message----- From: Frederic Rossi (LMC) [mailto:Fre...@er...] Sent: 2003=C4=EA6=D4=C221=C8=D5 2:10 To: Fan, Ardelle Cc: Hu, Boris; aem...@li... Subject: Re: AEM work It's not the way it work. If you plan to contribute I firmly encourage you to first download the source code, try it out, and get the exact idea of what we are trying to acheive. You can use this mailing list to send patches or communicate, it's a good idea. You want to use AEM to do what exactly? I you need this type of mechanism, you probably know better than me which feature to implement. But if you just want to contribute, once again, I have no problem with, this but you have to show you understood what AEM does first. F. ----- Original Message ----- From: "Fan, Ardelle" <ard...@in...> To: "Frederic Rossi (LMC)" <Fre...@er...> Cc: "Hu, Boris" <bor...@in...>; <aem...@li...> Sent: Friday, June 20, 2003 4:18 AM Subject: AEM work Hi Frederic Could you please add me and Boris to the developer list? Thank you. My sf account is ardelle_fan. Boris's is boris_hu. We will setup the environment and run the testsuite to have a taste first. :) From cgl-discussion mailing list, there is several line in PoC Meeting Minutes 6/19/03 that: " ...... Opens ----- AEM to be submitted to lkml. ...... " Have you seen that? Could I know your plan of AEM submission to lkml? And I think we'd better settle down a TODO list for several monthes. So t= hat we can read the source with focus and plan our long term development tasks. According to your mail, it seems that SMP stabilization is a feature we could focus on. How do you estimate the gap between current 2.5 implementation and the standard of being accepted by lkml? I am considering that it is also a go= od point for us. And when I read through the "OSDL CGL Requirements for Low-Level Asynchronous Events", there are a lot of Priority 2 features required. According to that document, p2 is for CGL3.0. But on the base of a stable AEM on both UP and SMP, and also acceptable to lkml, could we choose some imortant features implemented in CGL2.0? One more question, is all P1 features implemented in current 2.5.60 patch? Sorry for so many questions and thanks for your help! Ardelle Fan Software Engineer, Intel Corporation ard...@in... These are my opinions and absolutely not official opinions of Intel Corp. |
|
From: Fan, A. <ard...@in...> - 2003-06-23 08:47:08
|
Hi Frederic Maybe we were too hurried. We have already downloaded the source code = and went through roughly. And now we are setting up the environment and trying all test cases. As for our intention about AEM, to be frankly, we just hope to = contribute. We really wish to do some help to AEM project. UP/SMP issue is a good point and we are investigating from test case to = reproduce the problem. Could you tell us how=20 did you find that it has this kind of issue? running some test case or = just leave it with some days to see it hang (or crash)? We plan to first reproduce it and try to shorten the time before hang = happens in order to ease future debugging. How do you think about it? And any suggestion about it? And here is another thing we found in our try: In = aem-testsuite-v0.3/Timer_Pkg, when we pass the command "./timer 0", 5 = timer is created. And then there are several lines of timeout messages showing up the = screen. After that the linux box(SMP) hung in about ten seconds. I know that 0 is not a valid parameter for the timer interval. I just want to = see what will happen in such edge condition. Can we take it as the symptom of the UP/SMP issue? In last mail I have asked the TODO list, because SMP issue can be a = global and deep hidden bug. Maybe some small feature support can be some threads for us to get hands dirty. If you think = there isn't any available for us, just forget about it. Thank you Regards/Ardelle -----Original Message----- From: Frederic Rossi (LMC) [mailto:Fre...@er...] Sent: 2003=C4=EA6=D4=C221=C8=D5 2:10 To: Fan, Ardelle Cc: Hu, Boris; aem...@li... Subject: Re: AEM work It's not the way it work. If you plan to contribute I firmly encourage you to first download the source code, try it out, and get the exact idea of what we are trying to acheive. You can use this mailing list to send patches or communicate, it's a good idea. You want to use AEM to do what exactly? I you need this type of mechanism, you probably know better than me which feature to implement. But if you just want to contribute, once again, I have no problem with, this but you have to show you understood what AEM does first. F. ----- Original Message ----- From: "Fan, Ardelle" <ard...@in...> To: "Frederic Rossi (LMC)" <Fre...@er...> Cc: "Hu, Boris" <bor...@in...>; <aem...@li...> Sent: Friday, June 20, 2003 4:18 AM Subject: AEM work Hi Frederic Could you please add me and Boris to the developer list? Thank you. My sf account is ardelle_fan. Boris's is boris_hu. We will setup the environment and run the testsuite to have a taste = first. :) From cgl-discussion mailing list, there is several line in PoC Meeting Minutes 6/19/03 that: " ...... Opens ----- AEM to be submitted to lkml. ...... " Have you seen that? Could I know your plan of AEM submission to lkml? And I think we'd better settle down a TODO list for several monthes. So = that we can read the source with focus and plan our long term development tasks. According to your mail, it seems that SMP stabilization is a feature we could focus on. How do you estimate the gap between current 2.5 implementation and the standard of being accepted by lkml? I am considering that it is also a = good point for us. And when I read through the "OSDL CGL Requirements for Low-Level Asynchronous Events", there are a lot of Priority 2 features required. According to that document, p2 is for CGL3.0. But on the base of a = stable AEM on both UP and SMP, and also acceptable to lkml, could we choose = some imortant features implemented in CGL2.0? One more question, is all P1 features implemented in current 2.5.60 patch? Sorry for so many questions and thanks for your help! Ardelle Fan Software Engineer, Intel Corporation ard...@in... These are my opinions and absolutely not official opinions of Intel = Corp. |
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-06-20 18:10:58
|
It's not the way it work. If you plan to contribute I firmly encourage you to first download the source code, try it out, and get the exact idea of what we are trying to acheive. You can use this mailing list to send patches or communicate, it's a good idea. You want to use AEM to do what exactly? I you need this type of mechanism, you probably know better than me which feature to implement. But if you just want to contribute, once again, I have no problem with, this but you have to show you understood what AEM does first. F. ----- Original Message ----- From: "Fan, Ardelle" <ard...@in...> To: "Frederic Rossi (LMC)" <Fre...@er...> Cc: "Hu, Boris" <bor...@in...>; <aem...@li...> Sent: Friday, June 20, 2003 4:18 AM Subject: AEM work Hi Frederic Could you please add me and Boris to the developer list? Thank you. My sf account is ardelle_fan. Boris's is boris_hu. We will setup the environment and run the testsuite to have a taste first. :) From cgl-discussion mailing list, there is several line in PoC Meeting Minutes 6/19/03 that: " ...... Opens ----- AEM to be submitted to lkml. ...... " Have you seen that? Could I know your plan of AEM submission to lkml? And I think we'd better settle down a TODO list for several monthes. So that we can read the source with focus and plan our long term development tasks. According to your mail, it seems that SMP stabilization is a feature we could focus on. How do you estimate the gap between current 2.5 implementation and the standard of being accepted by lkml? I am considering that it is also a good point for us. And when I read through the "OSDL CGL Requirements for Low-Level Asynchronous Events", there are a lot of Priority 2 features required. According to that document, p2 is for CGL3.0. But on the base of a stable AEM on both UP and SMP, and also acceptable to lkml, could we choose some imortant features implemented in CGL2.0? One more question, is all P1 features implemented in current 2.5.60 patch? Sorry for so many questions and thanks for your help! Ardelle Fan Software Engineer, Intel Corporation ard...@in... These are my opinions and absolutely not official opinions of Intel Corp. |
|
From: Fan, A. <ard...@in...> - 2003-06-20 08:18:22
|
Hi Frederic Could you please add me and Boris to the developer list? Thank you. My sf account is ardelle_fan. Boris's is boris_hu. We will setup the environment and run the testsuite to have a taste = first. :) From cgl-discussion mailing list, there is several line in PoC Meeting = Minutes 6/19/03 that: " ...... Opens ----- AEM to be submitted to lkml. ...... " Have you seen that? Could I know your plan of AEM submission to lkml? And I think we'd better settle down a TODO list for several monthes. So = that we can read the source with focus and plan our long term development tasks. According to your mail, it seems that SMP stabilization is a feature we = could focus on. How do you estimate the gap between current 2.5 implementation and the = standard of being accepted by lkml? I am considering that it is also a = good point for us. And when I read through the "OSDL CGL Requirements for Low-Level = Asynchronous Events", there are a lot of Priority 2 features required. According to that document, p2 is for CGL3.0. But on the base of a = stable AEM on both UP and SMP, and also acceptable to lkml, could we = choose some imortant features implemented in CGL2.0? One more question, = is all P1 features implemented in current 2.5.60 patch? Sorry for so many questions and thanks for your help! Ardelle Fan Software Engineer, Intel Corporation ard...@in... These are my opinions and absolutely not official opinions of Intel = Corp. |
|
From: Philippe M. (LMC) <Phi...@er...> - 2003-05-01 13:37:02
|
The AEM StabilizationSuite and the TestSuite v0.3 are now available for download. Major changes : - All Applications have been changed to suit the new API of the AEM patch 12rX - There is now a global makefile in the AsyncServer-5_Pkg - Minor changes to the TimerStarter application - Epoll server in the Stabilizator has been changed to behave as the asyncServer if Epoll isn't installed In order to try it out you first need to dowload and install the AEM patch version 12rX for your kernel.Other instructions are provided by Readme files inside the package. The AEM StabilizationSuite and TestSuite can be downloaded from the CVS server at http://sourceforge.net/projects/aem |
|
From: Philippe M. (LMC) <Phi...@er...> - 2003-04-04 14:40:15
|
The AEM StabilizationSuite-v0.2 is now available for download.
Major changes :
- New location for overall Makefile, executables are now in bin/ directory
and results in Results/ directory in root directory.
- Changed permission of newly created files so the tests can be run
if you're not logged as root
- Makefiles test if /dev/epoll is installed before compiling asyncServerEpoll
If it isn't installed, asyncServerEpoll is replaced by asyncServer.
In order to try it out you first need to dowload and install the
latest AEM patch for your kernel. It worked very well with the
version 11r6 of the kernel patch. Other instructions are provided by
Readme files inside the package.
The AEM StabilizationSuite-v0.2 can be downloaded from the CVS server at
http://sourceforge.net/projects/aem or from the AEM home page at
http://aem.sourceforge.net
|
|
From: Philippe M. (LMC) <Phi...@er...> - 2003-03-28 18:12:42
|
The AEM testsuitev0.2 is now available for download. It has been modified to suit the new API of the AEM patch for kernel 11r0. It has now two new server. They are a cross implementation of AEM read handler and another interface. The first one uses select() to handle message larger than the MTU and the second one uses /dev/epoll. It also has a new client that send messages according to the message size instead of the message content. More information is available in the updated README. You can download AEM directly from the CVS server at http://sourceforge.net/projects/aem or from the AEM home page at http://aem.sourceforge.net |
|
From: Philippe M. (LMC) <Phi...@er...> - 2003-03-27 18:44:20
|
The AEM StabilizationSuite v0.1 is now available for download. It contains the source code of automated tests with various types of server, such as a cross implementation of AEM and epoll or select(). The tests can be made remotelly of locally. In order to try it out you first need to dowload and install the latest AEM patch for your kernel. It worked very well with the version 11r3 of the kernel patch. Other instructions are provided by Readme files inside the package. The AEM StabilizationSuite-v0.1 can be dowloaded from the CVS server at http://sourceforge.net/projects/aem or from the AEM home page at http://aem.sourceforge.net |
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-03-17 16:32:19
|
There has been some changes in the user API for the
patch linux-2.4.19-aem-11r0.
* evctl calling convention:
unsigned long evctl (parent_id, flags, jid);
* When requesting a memory pool inside the brk area,
the application has to populate the change to the
glibc library. The way of doing it is:
#define TBL_UZONE 0
void *new_brk;
new_brk = (void *)evctl (0, EVTBLINIT, TBL_UZONE);
brk (new_brk);
* Events are disabled now after their registration. This
means that the application must start them explicitly.
- EVJOBSTART: start/enable a job monitoring an
event.
ex: evctl (parent_id, EVJOBSTART, jid);
where jid is the job to enable.
ex: evctl (parent_id, EVJOBSTART, -1);
enables all jobs belonging to the current process.
- EVJOBSTOP: stop/disbale a job monitoring an
event.
ex: evctl (parent_id, EVJOBSTOP, jid);
where jid is the job to disable.
ex: evctl (parent_id, EVJOBSTOP, -1);
disables all jobs belonging to the current process.
* There is some moification regarding the calling convention for
the flag EVJOBSHTDN.
- EVJOBSHTDN: shutdown a job.
ex: evctl (parent_id, EVJOBSHTDN, jid);
where jid is the job to shutdown.
ex: evctl (parent_id, EVJOBSHTDN, -1);
shutdown all jobs belonging to the current process.
|
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-03-17 16:04:35
|
The AEM patch version linux-2.4.19-aem-11r0 is now avalaible for download. It includes some bug fixes and corrections. See below for details. You can download AEM directly from the CVS server at http://sourceforge.net/projects/aem or from the AEM home page at http://aem.sourceforge.net 2003/03/10 * mm/vmtables.c: + Lot of fixes. + Now we allocate contiguous pages for both brk and mmap. + Reduced the pool size to 130Kb. 2003/02/25 * arch/i386/kernel/signal.c: + Corrected signal handling. Signals are now running atomically w.r.t events. 2003/02/25 * kernel/event.c + Added a job start and job stop flag for evctl + jobs can now shtdn one or more jobs. 2003/02/25 * Events are started disabled now. So they must be explicitly enabled by the application (ex: evctl (job, EVJOBSTART, jid)). |
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-02-12 14:12:32
|
The AEM patch version Linux-2.4.19-aem-10r12 is now avalaible for download. It includes some bug fixes and corrections. See below for details. You can download AEM from the CVS server at http://sourceforge.net/projects/aem or from the AEM home page at http://aem.sourceforge.net 2003/02/11 * mm/vmtables.c: + Prefetch mapped addresses. 2003/02/11 * include/linux/sched.h: + Added the decl_asm_symbol() macro to export task_struct member offset into the assembler code. 2003/02/11 * arch/i386/kernel/entry.S + Fixed the keep_alive variable handling. It is now declared with decl_asm_symbol(). |
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-02-06 18:22:08
|
The AEM testsuite v0.1 is now available for download. It contains the source code for client and server programs showing how to use AEM for asynchronous TCP communication and soft timers. In order to try it out you first need to dowload and install the AEM patch for your kernel. Other instructions are provided by Readme files inside the package. The AEM testsuite-v0.1 can be dowloaded from the CVS server at http://sourceforge.net/projects/aem or from the AEM home page at http://aem.sourceforge.net |
|
From: Frederic R. (LMC) <Fre...@er...> - 2003-02-06 13:47:37
|
The AEM patch version Linux-2.4.19-aem-10r11 is now avalaible for
download.
It includes some bug fixes and corrections. See below for details.
You can download AEM from the CVS server at
http://sourceforge.net/projects/aem
or from the AEM home page at http://aem.sourceforge.net
2003/02/04
* mm/vmtables.c:
+ Fixed some bugs. Corrected vmtable_unmap().
2003/02/05
* kernel/events.c:
+ Fixed do_event. Do not restart a job if the event is shutting down.
(provoked many occurances of the same event in the case of event
processes).
+ Now we test before starting the event if the job has been marked
has shutting down.
+ Fixed forget_child. For some reason the (new) parent wont start.
+ Minor fixes.
2003/02/05
* net/tcpa_read.c:
+ Now shutdown the job if the socket is closing.
|
