Re: writev() "bug"

Matthias Urlichs (smurf@smurf.noris.de)
Wed, 5 Jun 1996 20:16:50 +0100

In linux.dev.kernel, article <199606031652.RAA32630@snowcrash.cymru.net=
>,
Alan Cox <alan@cymru.net> writes:
> > Not necessary. As of libc 5.2.18, libc writev()s longer vectors MA=
X_IOVEC
> > iov's at a time. The only problem occurs when you use a library co=
mpiled
>=20
> Then libc is broke writev/readv makes atomicity guarantees.
>=20
That's not a libc problem, that's the kernel. (Assuming that we're not
talking about sockets here.)

--=20
The San Francisco Giants were sued for giving away Father's Day gifts=20
to men only.
--=20
Matthias Urlichs \ noris network GmbH / Xlink-POP N=FCrnberg=
=20
Schleiermacherstra=DFe 12 \ Linux+Internet / EMail: urlichs@nor=
is.de
90491 N=FCrnberg (Germany) \ Consulting+Programming+Networking+etc=
'ing
PGP: 1024/4F578875 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 D=
E
Click <A HREF=3D"http://info.noris.de/~smurf/finger">here</A>. =
42