Sujet : Re: Python (was Re: I did not inhale)
De : invalid (at) *nospam* invalid.invalid (Richard Kettlewell)
Groupes : comp.unix.shell comp.unix.programmer comp.lang.miscDate : 18. Aug 2024, 23:15:53
Autres entêtes
Organisation : terraraq NNTP server
Message-ID : <wwvle0tbkhi.fsf@LkoBDZeT.terraraq.uk>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
User-Agent : Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Muttley@dastardlyhq.com writes:
Most (all?) versions of unix use copy-on-write when forking so while the
processes are only reading its no different to threading. I doubt windows
implements CoW since - in user space at least - it can't do fork and you
wouldn't need it for executing a brand new process from scratch.
It does. It’s still a handy optimization for the mutable parts of
executables and (particularly) shared libraries even in the absence of
fork.
AIUI the kernel API gives you enough to implement fork (and that’s how
the POSIX subsystem worked when that was still a thing), but good luck
finding any public documentation about it.
Windows sockets are not integers,
They are an unsigned integer type, I think 64 bits currently.
-- https://www.greenend.org.uk/rjk/