The Design and Implementation of the FreeBSD Operating System, Second Edition
Now available: The Design and Implementation of the FreeBSD Operating System, Second Edition

[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]

FreeBSD/Linux Kernel Cross Reference
sys/man/memory_object_data_unavailable.man

Version: -  FREEBSD  -  FREEBSD10  -  FREEBSD9  -  FREEBSD92  -  FREEBSD91  -  FREEBSD90  -  FREEBSD8  -  FREEBSD82  -  FREEBSD81  -  FREEBSD80  -  FREEBSD7  -  FREEBSD74  -  FREEBSD73  -  FREEBSD72  -  FREEBSD71  -  FREEBSD70  -  FREEBSD6  -  FREEBSD64  -  FREEBSD63  -  FREEBSD62  -  FREEBSD61  -  FREEBSD60  -  FREEBSD5  -  FREEBSD55  -  FREEBSD54  -  FREEBSD53  -  FREEBSD52  -  FREEBSD51  -  FREEBSD50  -  FREEBSD4  -  FREEBSD3  -  FREEBSD22  -  cheribsd  -  linux-2.6  -  linux-2.4.22  -  MK83  -  MK84  -  PLAN9  -  DFBSD  -  NETBSD  -  NETBSD5  -  NETBSD4  -  NETBSD3  -  NETBSD20  -  OPENBSD  -  xnu-517  -  xnu-792  -  xnu-792.6.70  -  xnu-1228  -  xnu-1456.1.26  -  xnu-1699.24.8  -  xnu-2050.18.24  -  OPENSOLARIS  -  minix-3-1-1  -  FREEBSD-LIBC  -  FREEBSD8-LIBC  -  FREEBSD7-LIBC  -  FREEBSD6-LIBC  -  GLIBC27 
SearchContext: -  none  -  3  -  10 

    1 .\" 
    2 .\" Mach Operating System
    3 .\" Copyright (c) 1991,1990 Carnegie Mellon University
    4 .\" All Rights Reserved.
    5 .\" 
    6 .\" Permission to use, copy, modify and distribute this software and its
    7 .\" documentation is hereby granted, provided that both the copyright
    8 .\" notice and this permission notice appear in all copies of the
    9 .\" software, derivative works or modified versions, and any portions
   10 .\" thereof, and that both notices appear in supporting documentation.
   11 .\" 
   12 .\" CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
   13 .\" CONDITION.  CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR
   14 .\" ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
   15 .\" 
   16 .\" Carnegie Mellon requests users of this software to return to
   17 .\" 
   18 .\"  Software Distribution Coordinator  or  Software.Distribution@CS.CMU.EDU
   19 .\"  School of Computer Science
   20 .\"  Carnegie Mellon University
   21 .\"  Pittsburgh PA 15213-3890
   22 .\" 
   23 .\" any improvements or extensions that they make and grant Carnegie Mellon
   24 .\" the rights to redistribute these changes.
   25 .\" 
   26 .\" 
   27 .\" HISTORY
   28 .\" $Log:       memory_object_data_unavailable.man,v $
   29 .\" Revision 2.5  93/05/10  19:33:40  rvb
   30 .\"     updated
   31 .\"     [93/04/21  16:08:24  lli]
   32 .\" 
   33 .\" Revision 2.4  91/05/14  17:09:18  mrt
   34 .\"     Correcting copyright
   35 .\" 
   36 .\" Revision 2.3  91/02/14  14:12:54  mrt
   37 .\"     Changed to new Mach copyright
   38 .\"     [91/02/12  18:13:23  mrt]
   39 .\" 
   40 .\" Revision 2.2  90/08/07  18:40:26  rpd
   41 .\"     Created.
   42 .\" 
   43 .TH memory_object_data_unavailable 2 12/18/89
   44 .CM 4
   45 .SH NAME
   46 .nf
   47 memory_object_data_unavailable  \-  indicates non-existent data
   48 .SH SYNOPSIS
   49 .nf
   50 .ft B
   51 #include <mach.h>
   52 
   53 .nf
   54 .ft B
   55 kern_return_t memory_object_data_unavailable(memory_control,
   56                                 offset, size);
   57         mach_port_t
   58                         memory_control;
   59         vm_offset_t     offset;
   60         vm_size_t       size;
   61 
   62 
   63 .fi
   64 .ft P
   65 .SH DESCRIPTION
   66 
   67 .B memory_object_data_unavailable
   68 indicates that the memory object does not
   69 have data for the given region and that the kernel should provide the
   70 data for this range. The memory manager may use this call in three different
   71 situations. 1) The object was created by 
   72 .B memory_object_create
   73 and the kernel
   74 has not yet provided data for this range (either via a 
   75 .B memory_object_data_initialize
   76 or a 
   77 .B memory_object_data_write
   78 . In this case the kernel should supply zero-filled pages
   79 for the object. 2) The object was created by an 
   80 .B memory_object_data_copy
   81 and the kernel should copy this region from the original memory object. 3) The object
   82 is a normal user-created memory object and the kernel should supply unlocked zero-filled
   83 pages for the range.
   84 
   85 .SH ARGUMENTS
   86 .TP 15
   87 .B
   88 memory_control
   89 The port, provided by the kernel 
   90 in a 
   91 .B memory_object_init
   92 call, to which cache management requests may be issued.
   93 .TP 15
   94 .B
   95 offset
   96 An offset within a memory object, in bytes.  This must be
   97 page aligned.
   98 .TP 15
   99 .B
  100 size
  101 The amount of cached data (starting at 
  102 .B offset
  103 ) to be handled. This
  104 must be an integral multiple of the memory object page size.
  105 
  106 .SH DIAGNOSTICS
  107 .TP 25
  108 KERN_SUCCESS
  109 This routine does not receive a reply message (and consequently
  110 has no return value), so only message transmission errors apply.
  111 
  112 .SH SEE ALSO
  113 .B memory_object_create, memory_object_data_request, memory_object_data_error
  114 

Cache object: a9b27b89750e0185f23cd232638bb70a


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]


This page is part of the FreeBSD/Linux Linux Kernel Cross-Reference, and was automatically generated using a modified version of the LXR engine.