This wiki article contains incomplete and informal notes about the MPS, the precursor to more formal documentation. Not confidential. Readership: MPS users and developers.

Introduction

This is an approximate timeline of significant changes to the MPS.

Timeline

Date Chg Area Change
1998-11-10 21000 Arena↔Pool "Sunset on Segments": Segments can now be of arbitrary size, and are composed of one or more contiguous fixed-size Tracts (Previously Segments were fixed-size).
2001-03-02 ? Scheduling Chains (of generations) for AMC, AMS, LO, and AWL, replacing Actions (action.c)
2002-05-24 29464 Scheduling Opportunism: mps_arena_step()
2003-02-17 39673 Scheduling Opportunism 2: mps_arena_step(..., interval, multiplier)
2008-11-07 166676 Message add postedClock field to messages; move message type from MessageStruct to MessageClassStruct
2008-12-19 166995 Message _gc_start message lifecycle was thoroughly broken; fix it.
2009-09-18 168761 PoolAMC AMC Large Segment Padding to reduce risk of pathological ambiguous retention. PoolTraceEnd methods.

B. Document History

  2006-11-27  RHSK  Created.
  2007-04-26  RHSK  1998-11-10: Sunset on segments
  2008-11-07  RHSK  2008-11-07: Message changes
  2010-03-03  RHSK  2008-12-19: _gc_start message fix; 2009-09-18 AMC LSP.

C. Copyright and License

This document is copyright © 2006, 2007, 2008, 2010 Ravenbrook Limited. All rights reserved. This is an open source license. Contact Ravenbrook for commercial licensing options.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. Redistributions in any form must be accompanied by information on how to obtain complete source code for the this software and any accompanying software that uses this software. The source code must either be included in the distribution or be available for no more than the cost of distribution plus a nominal fee, and must be freely redistributable under reasonable conditions. For an executable file, complete source code means the source code for all modules it contains. It does not include source code for modules or files that typically accompany the major components of the operating system on which the executable file runs.

This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement, are disclaimed. In no event shall the copyright holders and contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.