Changes between Version 1 and Version 2 of Projects/GSoC/PosixKeys


Ignore:
Timestamp:
Aug 19, 2012, 3:16:29 PM (7 years ago)
Author:
Zhongwei Yao
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Projects/GSoC/PosixKeys

    v1 v2  
    55There are 2 problems in current implementation of POSIX Key(more details are described next section).
    66#The POSIX key area is not properly extended when the number of threads is increased(dynamically created) if POSIX threads are configured as "unlimited", which is a known bug.
    7 #Extra memory is reserved in keys for each thread or task in current implementation, which can be heavy memory overhead when keys increase.
     7#Extra memory is reserved in keys for each thread or task in current implementation, which can be heavy memory overhead when keys increase.=  several design approaches  =
     8=  current implementation  =
     9
     10current implementation allocates an array when key creates, which holds all of the threads' or tasks' key value. The pre-allocated array's size is as big as the number of threads in system. It is a waste of memory that allocates key value slot for thread which would not use POSIX key at all. And other problems of current implementation is as [wiki:Current_implementation's_problem current implementation's problem] describes.