Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 05 Sep 2004 22:37:31 +0200
From:      Christian Brueffer <chris@unixpages.org>
To:        Alan Cox <alc@cs.rice.edu>
Cc:        cvs-all@freebsd.org
Subject:   Re: cvs commit: src/lib/libc/sys msync.2
Message-ID:  <20040905203730.GH66117@unixpages.org>
In-Reply-To: <20040905194632.GK10220@cs.rice.edu>
References:  <200409030624.i836OPaL018916@repoman.freebsd.org> <20040905194632.GK10220@cs.rice.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

--KaGhPsiNaI6/sRd6
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Sep 05, 2004 at 02:46:32PM -0500, Alan Cox wrote:
> On Sat, Sep 04, 2004 at 09:30:43PM -0400, David Schultz wrote:
> > On Fri, Sep 03, 2004, Peter Pentchev wrote:
> > > roam        2004-09-03 06:24:25 UTC
> > >=20
> > >   FreeBSD src repository (doc,ports committer)
> > >=20
> > >   Modified files:
> > >     lib/libc/sys         msync.2=20
> > >   Log:
> > >   Add a BUGS section and copy the wording from mmap(2)'s MAP_NOSYNC,
> > >   documenting the obsoleteness of the msync(2) syscall and its single
> > >   remaining purpose.
> >=20
> > I'm not nitpicking at you since you didn't write the original
> > text, but if msync(2) still has a purpose, then it isn't really
> > obsolete, is it?  (Moreover, the text only describes the purpose of
> > msync(2) with the MS_ASYNC flag.)  Applications such as databases
> > that want greater control over the flushing of dirty data may
> > still find msync(2) very useful.
>=20
> I agree.  This sentence should be removed from both msync.2 and mmap.2
> for precisely the reason you state.
>=20
> It is, however, worth mentioning that FreeBSD has a unified buffer and
> virtual memory page cache in these man pages.  In fact, that does make
> most uses of msync()'s MS_INVALIDATE flag unnecessary.  (The useful cases
> being things like the extension used by the Nvidia driver.)
>=20
> On a related note, where do we stand with respect to the use of X/Open
> man pages?  The X/Open man page for msync(2) is much better than ours.
>=20

"The IEEE and The Open Group have granted permission to the FreeBSD
Project to incorporate material from the joint IEEE 1003.1\x{2122}
POSIX=AE standard and The Open Group Base Specifications Issue 6."

http://www.opengroup.org/press/01jun04.htm

- Christian

--=20
Christian Brueffer	chris@unixpages.org	brueffer@FreeBSD.org
GPG Key:	 http://people.freebsd.org/~brueffer/brueffer.key.asc
GPG Fingerprint: A5C8 2099 19FF AACA F41B  B29B 6C76 178C A0ED 982D

--KaGhPsiNaI6/sRd6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFBO3kKbHYXjKDtmC0RAtS9AJsHdpvbaj3+zfbzv8v6vLfn4CkzcQCg5uIx
R7w2+znlGFjuIS3Ce03WCUg=
=eoKj
-----END PGP SIGNATURE-----

--KaGhPsiNaI6/sRd6--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040905203730.GH66117>