skip to main | skip to sidebar

Logging All things open source

Saturday, February 2, 2008

System V shared memory
System V provides an alternative mechanism for setting up shared memory, via the shmctl (), shmget (), shmat (), and shmdt () set of calls. These are not suggested for use, because
  • System V entities live in a seperate namespace with seperate access permissions and adminstrative tools (e.g., ipcs).
  • System V entities are not automatically cleaned up if all programs using them exit, and can be a resource management nightmare.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Newer Post Older Post Home

Shared items

Blog Archive

  • ►  2010 (1)
    • ►  February (1)
  • ►  2009 (12)
    • ►  December (2)
    • ►  October (1)
    • ►  September (1)
    • ►  April (2)
    • ►  February (5)
    • ►  January (1)
  • ▼  2008 (94)
    • ►  December (2)
    • ►  October (4)
    • ►  September (2)
    • ►  August (1)
    • ►  July (15)
    • ►  June (37)
    • ►  May (7)
    • ▼  February (8)
      • Event Handling Frameworklibevent provides a simple...
      • Ken Thompson Refelections on Trusting TrustBTW if ...
      • Unix Memory ModelThere are some basic regions ("se...
      • System V shared memorySystem V provides an alterna...
      • Shared memoryPhysical memory can be shared between...
      • mmapThe mmap () system call allows the programmer...
      • Unix SignalsSignals are an asynchronous notificati...
      • Event ServerServers typically handle three types o...
    • ►  January (18)

Chat with Me!