News for hackers. Stuff that matters.
Re:Global Interpreter Lock, or how to kill it by fijal on Wednesday June 29, 2011 @02:24PM (#2710588)
Two answers really:

* sharing memory - sometimes you have lots of immutable data, like modules, graphs, whatnot. Yes, there is copy-on-write and no, it doesn't work well on any python implementation out there. Also sometimes it's mostly-immutable data, but not quite.

* serializing lots of data is a mess and even if feasible is usually a big performance hit if you want to exchange actual objects.

Re:Global Interpreter Lock, or how to kill it by supersillyus on Wednesday June 29, 2011 @04:14PM (#2711055)
With Plan 9's rfork() (and linux's less nice clone()), you can create new processes that share the memory of the old process, which addresses those two answers. Though, I'm not sure if this reinforces OP's point or just indicates that the distinction between threads and processes can be fuzzy.
Re:Global Interpreter Lock, or how to kill it by mattgreenrocks on Thursday June 30, 2011 @12:32AM (#2712597)
What are the uses of a process that shares address space with its parent?
Re:Global Interpreter Lock, or how to kill it by Someone on Friday July 01, 2011 @04:23AM (#2717504)
I wondered, too, so I had to look this up http://cm.bell-labs.com/magic/man2html/2/fork shows that it is not the whole address space:

RFMEM If set, the child and the parent will share data and bss segments. Otherwise, the child inherits a copy of those segments. Other segment types, in particular stack segments, will be unaffected. May be set only with RFPROC.

So, it basically is a way to start a process that shares all its globals (including static variables, I think) with another process, but not other memory. That is more secure than having threads, but also more restricted, as one cannot share heap-allocated structures between such processes. I guess this feature gets used most in Fortran code where nothing gets allocated dynamically.

It also makes it easier to selective kill a thread of execution from the command line, but I do not see when that might be useful.