src/os/bsd/vm/perfMemory_bsd.cpp

rev 2698 : new bsd files

*** 25,35 ****
  #include "precompiled.hpp"
  #include "classfile/vmSymbols.hpp"
  #include "memory/allocation.inline.hpp"
  #include "memory/resourceArea.hpp"
  #include "oops/oop.inline.hpp"
! #include "os_linux.inline.hpp"
  #include "runtime/handles.inline.hpp"
  #include "runtime/perfMemory.hpp"
  #include "utilities/exceptions.hpp"
  
  // put OS-includes here
--- 25,35 ----
  #include "precompiled.hpp"
  #include "classfile/vmSymbols.hpp"
  #include "memory/allocation.inline.hpp"
  #include "memory/resourceArea.hpp"
  #include "oops/oop.inline.hpp"
! #include "os_bsd.inline.hpp"
  #include "runtime/handles.inline.hpp"
  #include "runtime/perfMemory.hpp"
  #include "utilities/exceptions.hpp"
  
  // put OS-includes here
*** 130,147 ****
  }
  
  
  // Shared Memory Implementation Details
  
! // Note: the solaris and linux shared memory implementation uses the mmap
  // interface with a backing store file to implement named shared memory.
  // Using the file system as the name space for shared memory allows a
  // common name space to be supported across a variety of platforms. It
  // also provides a name space that Java applications can deal with through
  // simple file apis.
  //
! // The solaris and linux implementations store the backing store file in
  // a user specific temporary directory located in the /tmp file system,
  // which is always a local file system and is sometimes a RAM based file
  // system.
  
  // return the user specific temporary directory name.
--- 130,147 ----
  }
  
  
  // Shared Memory Implementation Details
  
! // Note: the solaris and bsd shared memory implementation uses the mmap
  // interface with a backing store file to implement named shared memory.
  // Using the file system as the name space for shared memory allows a
  // common name space to be supported across a variety of platforms. It
  // also provides a name space that Java applications can deal with through
  // simple file apis.
  //
! // The solaris and bsd implementations store the backing store file in
  // a user specific temporary directory located in the /tmp file system,
  // which is always a local file system and is sometimes a RAM based file
  // system.
  
  // return the user specific temporary directory name.
*** 688,698 ****
  
  // create a named shared memory region. returns the address of the
  // memory region on success or NULL on failure. A return value of
  // NULL will ultimately disable the shared memory feature.
  //
! // On Solaris and Linux, the name space for shared memory objects
  // is the file system name space.
  //
  // A monitoring application attaching to a JVM does not need to know
  // the file system name of the shared memory object. However, it may
  // be convenient for applications to discover the existence of newly
--- 688,698 ----
  
  // create a named shared memory region. returns the address of the
  // memory region on success or NULL on failure. A return value of
  // NULL will ultimately disable the shared memory feature.
  //
! // On Solaris and Bsd, the name space for shared memory objects
  // is the file system name space.
  //
  // A monitoring application attaching to a JVM does not need to know
  // the file system name of the shared memory object. However, it may
  // be convenient for applications to discover the existence of newly