*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->FreeBSD man pages -> minherit (2)              
Title
Content
Arch
Section
 

MINHERIT(2)

Contents


NAME    [Toc]    [Back]

     minherit -- control the inheritance of pages

LIBRARY    [Toc]    [Back]

     Standard C Library (libc, -lc)

SYNOPSIS    [Toc]    [Back]

     #include <sys/mman.h>

     int
     minherit(void *addr, size_t len, int inherit);

DESCRIPTION    [Toc]    [Back]

     The minherit() system call changes the specified pages to have the inheritance
 characteristic inherit.  Not all implementations will guarantee
     that the inheritance characteristic can be set on a page basis; the granularity
 of changes may be as large as an entire region.  FreeBSD is capable
 of adjusting inheritance characteristics on a page basis.  Inheritance
 only effects children created by fork().  It has no effect on
     exec().  exec'd processes replace their address space entirely.  This
     system call also has no effect on the parent's address space (other than
     to potentially share the address space with its children).

     Inheritance is a rather esoteric feature largely superseded by the
     MAP_SHARED feature of mmap().  However, it is possible to use minherit()
     to share a block of memory between parent and child that has been mapped
     MAP_PRIVATE.  That is, modifications made by parent or child are shared
     but the original underlying file is left untouched.

     INHERIT_SHARE  This option causes the address space in question to be
		    shared between parent and child.  It has no effect on how
		    the original underlying backing store was mapped.

     INHERIT_NONE   This option prevents the address space in question from
		    being inherited at all.  The address space will be
		    unmapped in the child.

     INHERIT_COPY   This option causes the child to inherit the address space
		    as copy-on-write.  This option also has an unfortunate
		    side effect of causing the parent address space to become
		    copy-on-write when the parent forks.  If the original mapping
 was MAP_SHARED, it will no longer be shared in the
		    parent after the parent forks and there is no way to get
		    the previous shared-backing-store mapping without unmapping
 and remapping the address space in the parent.

RETURN VALUES    [Toc]    [Back]

     The minherit() function returns the value 0 if successful; otherwise the
     value -1 is returned and the global variable errno is set to indicate the
     error.

ERRORS    [Toc]    [Back]

     The minherit() system call will fail if:

     [EINVAL]		The virtual address range specified by the addr and
			len arguments is not valid.

     [EACCES]		The flags specified by the inherit argument were not
			valid for the pages specified by the addr and len
			arguments.

BUGS    [Toc]    [Back]

     Once you set inheritance to MAP_PRIVATE or MAP_SHARED, there is no way to
     recover the original copy-on-write semantics short of unmapping and
     remapping the area.

SEE ALSO    [Toc]    [Back]

      
      
     fork(2), madvise(2), mincore(2), mprotect(2), msync(2), munmap(2),
     rfork(2)

HISTORY    [Toc]    [Back]

     The minherit() system call first appeared in OpenBSD.


FreeBSD 5.2.1		       February 17, 1996		 FreeBSD 5.2.1
[ Back ]
 Similar pages
Name OS Title
mprotect FreeBSD control the protection of pages
mprotect OpenBSD control the protection of pages
mprotect NetBSD control the protection of pages
iflClassList IRIX class inheritance chain
vm_map_inherit FreeBSD set fork inheritance flags for a range within a map
pthread_attr_setinheritsched IRIX thread scheduling inheritance attributes
mmap IRIX map pages of memory
mmap HP-UX map pages of memory
catman FreeBSD preformat man pages
miscellaneous FreeBSD miscellaneous information pages
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service