Index: ossp-pkg/mm/ChangeLog RCS File: /v/ossp/cvs/ossp-pkg/mm/ChangeLog,v rcsdiff -q -kk '-r1.53' '-r1.54' -u '/v/ossp/cvs/ossp-pkg/mm/ChangeLog,v' 2>/dev/null --- ChangeLog 2006/06/10 07:06:39 1.53 +++ ChangeLog 2006/06/10 07:07:54 1.54 @@ -15,6 +15,9 @@ GNU libtool 1.5.22 [Ralf S. Engelschall] + *) Fix spelling errors in manual page mm(3). + [Neil Conway ] + Changes between 1.3.1 and 1.4.0 (12-Sep-2003 to 02-Sep-2005) *) Optimize insertion of free memory chunks by merging with Index: ossp-pkg/mm/THANKS RCS File: /v/ossp/cvs/ossp-pkg/mm/THANKS,v rcsdiff -q -kk '-r1.17' '-r1.18' -u '/v/ossp/cvs/ossp-pkg/mm/THANKS,v' 2>/dev/null --- THANKS 2005/09/02 19:58:36 1.17 +++ THANKS 2006/06/10 07:07:54 1.18 @@ -21,6 +21,7 @@ o Jeff Clark o Albert Chin-A-Young o Eric Cholet + o Neil Conway o Alexander Demenchuk o Jason Dillon o Alexander Farber Index: ossp-pkg/mm/mm.pod RCS File: /v/ossp/cvs/ossp-pkg/mm/mm.pod,v rcsdiff -q -kk '-r1.24' '-r1.25' -u '/v/ossp/cvs/ossp-pkg/mm/mm.pod,v' 2>/dev/null --- mm.pod 2005/09/02 20:00:46 1.24 +++ mm.pod 2006/06/10 07:07:54 1.25 @@ -151,7 +151,7 @@ type `C' as its first argument. This API provides a comfortable way to work with small dynamically allocated shared memory chunks inside large statically allocated shared memory segments. It is internally based on the -I for creating the underlaying shared memory +I for creating the underlying shared memory segment. =item B @@ -221,7 +221,7 @@ =item 4.2BSD-style flock(2) on temporary file (FLOCK) I exists on a lot of platforms, especially on older Unix -derivates. I needs a temporary file on the filesystem and has +derivatives. I needs a temporary file on the filesystem and has to re-open file-descriptors to it in each(!) fork(2)'ed child process. =item SysV IPC semget(2) (IPCSEM) @@ -303,7 +303,7 @@ =item int B(mode_t I, uid_t I, gid_t I); This sets the filesystem I, I and I for the global shared -memory pool (has effects only if the underlaying shared memory segment +memory pool (has effects only if the underlying shared memory segment implementation is actually based on external auxiliary files). The arguments are directly passed through to chmod(2) and chown(2). @@ -391,7 +391,7 @@ =item int B(MM *I, mode_t I, uid_t I, gid_t I); This sets the filesystem I, I and I for the shared memory -pool I (has effects only when the underlaying shared memory segment +pool I (has effects only when the underlying shared memory segment implementation is actually based on external auxiliary files). The arguments are directly passed through to chmod(2) and chown(2). @@ -419,21 +419,21 @@ returns either a (virtual memory word aligned) pointer to it or C in case of an error (out of memory). It behaves like the POSIX.1 malloc(3) function but instead of allocating memory from the I it allocates it -from the shared memory segment underlaying I. +from the shared memory segment underlying I. =item void B(MM *I, void *I); This deallocates the chunk starting at I in the shared memory pool I. It behaves like the POSIX.1 free(3) function but instead of deallocating memory from the I it deallocates it from the shared memory segment -underlaying I. +underlying I. =item void *B(MM *I, void *I, size_t I); This function reallocates the chunk starting at I inside the shared memory pool I with the new size of I bytes. It behaves like the POSIX.1 realloc(3) function but instead of reallocating memory in the -I it reallocates it in the shared memory segment underlaying I. +I it reallocates it in the shared memory segment underlying I. =item void *B(MM *I, size_t I, size_t I); @@ -498,7 +498,7 @@ =item int B(void *I, mode_t I, uid_t I, gid_t I); This sets the filesystem I, I and I for the shared memory -segment I (has effects only when the underlaying shared memory segment +segment I (has effects only when the underlying shared memory segment implementation is actually based on external auxiliary files). The arguments are directly passed through to chmod(2) and chown(2). @@ -536,7 +536,7 @@ =item size_t B(size_t I); This is just a utility function which can be used to align the number I -to the next virtual memory I boundary used by the underlaying platform. +to the next virtual memory I boundary used by the underlying platform. The memory page boundary under Unix platforms is usually somewhere between 2048 and 16384 bytes. You do not have to align the I arguments of other B library functions yourself, because this is already done internally. @@ -546,12 +546,12 @@ =item size_t B(size_t I); This is another utility function which can be used to align the number I -to the next virtual memory I boundary used by the underlaying platform. +to the next virtual memory I boundary used by the underlying platform. The memory word boundary under Unix platforms is usually somewhere between 4 and 16 bytes. You do not have to align the I arguments of other B library functions yourself, because this is already done internally. This function is exported by the B library just for convenience reasons in case -an application wants to perform simular calculations for other purposes. +an application wants to perform similar calculations for other purposes. =back @@ -584,16 +584,16 @@ =head1 RESTRICTIONS The maximum size of a continuous shared memory segment one can allocate -depends on the underlaying platform. This cannot be changed, of course. But +depends on the underlying platform. This cannot be changed, of course. But currently the high-level malloc(3)-style API just uses a single shared memory -segment as the underlaying data structure for an C object which means that +segment as the underlying data structure for an C object which means that the maximum amount of memory an C object represents also depends on the platform. This could be changed in later versions by allowing at least the high-level malloc(3)-style API to internally use multiple shared memory segments to form the C object. This way C objects could have -arbitrary sizes, although the maximum size of an allocatable continous +arbitrary sizes, although the maximum size of an allocatable continuous chunk still is bounded by the maximum size of a shared memory segment. =head1 SEE ALSO