On Mon, Dec 12, 2011 at 09:11:02AM +1100, William ML Leslie wrote: > Well, you don't spend much time writing a kernel anyway - use an > existing kernel and then run python in userspace. It's pretty unusual > to need your code colocated with the kernel, but it would be easier to > do with a runtime like pypy (because of memory safety, you can > guarantee that code will never do anything that traps). I don't know > what you would do about interrupt handlers and GC.
This is somthing i have been playing with a tiny bit and seems to work well. i have a bunch of libs to interface directly to the linux syscalls, various c functions to specific libs that are useful and others to pull info out of /sys and /proc. it use the containerization/namespace stuff (same stuff LXC uses) in linux to isolate python in its own namespace. my intent is to make a primarily python userspace for my own personal usage and experiment with some new ideas as it is a namespace, i can still use the traditinol linux userspace to mange the hardware and for remote access/unbreaking things so esentially you get a managment domain and multiple self contained python based enviroments resource managment is done via cgroups instead of relying on pypy's memory limiting features due to the extra flexibility you gain (eg hieracal limitaiton on memory and swap usage, the ability to change allocations on the fly) _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
