freebsd-skq/lib/libc/sys/msync.2

126 lines
3.5 KiB
Groff
Raw Normal View History

1994-05-27 05:00:24 +00:00
.\" Copyright (c) 1991, 1993
.\" The Regents of the University of California. All rights reserved.
.\"
.\" 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. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR 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.
.\"
.\" @(#)msync.2 8.2 (Berkeley) 6/21/94
1999-08-28 00:22:10 +00:00
.\" $FreeBSD$
1994-05-27 05:00:24 +00:00
.\"
.Dd June 21, 1994
1994-05-27 05:00:24 +00:00
.Dt MSYNC 2
.Os
.Sh NAME
.Nm msync
.Nd synchronize a mapped region
.Sh LIBRARY
.Lb libc
1994-05-27 05:00:24 +00:00
.Sh SYNOPSIS
.In sys/mman.h
.Ft int
.Fn msync "void *addr" "size_t len" "int flags"
1994-05-27 05:00:24 +00:00
.Sh DESCRIPTION
The
.Fn msync
system call
writes any modified pages back to the file system and updates
1994-05-27 05:00:24 +00:00
the file modification time.
If
.Fa len
is 0, all modified pages within the region containing
.Fa addr
will be flushed;
if
.Fa len
2001-07-15 07:53:42 +00:00
is non-zero, only those pages containing
1994-05-27 05:00:24 +00:00
.Fa addr
and
.Fa len-1
1994-05-27 05:00:24 +00:00
succeeding locations will be examined.
The
.Fa flags
argument may be specified as follows:
2004-06-30 20:09:10 +00:00
.Pp
.Bl -tag -width ".Dv MS_INVALIDATE" -compact
.It Dv MS_ASYNC
Return immediately
.It Dv MS_SYNC
Perform synchronous writes
.It Dv MS_INVALIDATE
Invalidate all cached data
.El
.Sh RETURN VALUES
.Rv -std msync
.Sh ERRORS
The
.Fn msync
system call
will fail if:
.Bl -tag -width Er
.It Bq Er EBUSY
Some or all of the pages in the specified region are locked and
2004-06-30 20:09:10 +00:00
.Dv MS_INVALIDATE
is specified.
.It Bq Er EINVAL
2002-12-19 09:40:28 +00:00
The
.Fa addr
2002-12-19 09:40:28 +00:00
argument
is not a multiple of the hardware page size.
.It Bq Er EINVAL
2002-12-19 09:40:28 +00:00
The
.Fa len
2002-12-19 09:40:28 +00:00
argument
is too large or negative.
.It Bq Er EINVAL
2002-12-19 09:40:28 +00:00
The
.Fa flags
2002-12-19 09:40:28 +00:00
argument
was both MS_ASYNC and MS_INVALIDATE.
Only one of these flags is allowed.
2000-12-29 14:08:20 +00:00
.El
1994-05-27 05:00:24 +00:00
.Sh SEE ALSO
.Xr madvise 2 ,
.Xr mincore 2 ,
.Xr mlock 2 ,
1994-05-27 05:00:24 +00:00
.Xr mprotect 2 ,
1997-01-20 23:23:22 +00:00
.Xr munmap 2
1994-05-27 05:00:24 +00:00
.Sh HISTORY
The
.Fn msync
system call first appeared in
.Bx 4.4 .
.Sh BUGS
The
.Fn msync
system call is obsolete since
.Bx
implements a coherent file system buffer cache.
However, it may be used to associate dirty VM pages with file system
buffers and thus cause them to be flushed to physical media sooner
rather than later.