[cgl_discussion] RE: [cgl_specs] Proposal to change SCL.1.0 in CGL_Req spec
louis.zhuang at intel.com
Wed Jul 9 09:13:25 PDT 2003
If I understand the paper rightly, the real requirement is
"scalability in enormous events", and the asynchronous mechanism or
multi-threading are all "common ideas" to resolve the issue, right?
According to the paper, weakness of epoll is its focus on descriptor. So
my questions are,
1. If "asynchronous mechanism" is just a solution for real requirement,
is it absolutely necessary to put the implementation choice in spec?
2. epoll can only process descriptors... but as you know, descriptor can
represent almost everything in Unices (sockets, files, pipes and devices
etc.). Is it a real weakness?
Perhaps I lose some key points which demonstrate AEM's strength such as
'soft realtime'. But I think we need an agreement on definition in 'soft
RT' here. Any comments?
> -----Original Message-----
> From: Ibrahim Haddad (QB/LMC) [mailto:ibrahim.haddad at ericsson.com]
> Sent: Wednesday, July 09, 2003 11:07 PM
> To: Zhuang, Louis
> Cc: Fan, Ardelle; CGL Discussion; Linda Bebernes
> Subject: RE: [cgl_specs] Proposal to change SCL.1.0 in CGL_Req spec
> Hi Louis,
> I think the attached article will provide you with the answer.
> It provides the background on why we need something like aem,
> and to meet which requirements.
> ps: the zip file contains 1 html file + 2 png figures.
More information about the cgl_discussion