Subject: Re: fsync_range() system call
To: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 10/25/2003 13:27:16
--6lXr1rPCNTf1w0X8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Oct 26, 2003 at 02:35:43AM +0900, YAMAMOTO Takashi wrote:
> > This implementation copies the AIX system call of the same name. Includ=
ing=20
> > the requirement that the file descriptor be open for write for this cal=
l.=20
> > The call will cause the data in the range to be written, and also cause=
=20
> > some file metadata to be written.
>=20
> is the AIX version a cancellation point?
>=20
> at least, not listed here:
> http://publib16.boulder.ibm.com/pseries/en_US/aixprggd/genprogc/term_thre=
ads.htm

No, but to be honest I don't see why it isn't. fsync() is, so this one=20
really should be too.

The one thing that comes to mind is that that list looks very=20
standards-driven, so since fsync_range is an extension, it might have=20
gotten overlooked.

Take care,

Bill

--6lXr1rPCNTf1w0X8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQE/mtykWz+3JHUci9cRAqMTAKCLnkhr0enhmmYNI/P81EnuayEIAQCggWe5
9A3r9OovvsrVUZYrDbOfmSc=
=/IKC
-----END PGP SIGNATURE-----

--6lXr1rPCNTf1w0X8--