The meat eating world always seems to ignore the human ability to eat plants. I'm not going to say we shouldn't use silk worms. But human can eat the plants too. It would provide more variety and would probably make the diet healthier. So:
----> while (1) { plants(Sun, Fertiziler); silkworm(Plants); humans(Silkworm, Plants); }
It actually looks like the cylons gained sentients quite recently. Roughly 55 years before the series it looks like. The war 40 years before really was the first cylon war, cause they didn't exist before that.
And although I think the idea of repeated hybridization is cool it's not applicable to the show.
I thought that they minimized it in ways that the userspace switch could not. But I don't know much about the subject
Regardless it seems if the kernel knew about the driver processes it could reduce there latency even below what is possible with the "realtime" scheduler modes. Basically it could force a context switch to the driver as soon as important events occurred.
I would like to see a stabilized and standardized device interface API for standard devices, something exposing a limited subset of the kernel that would simplify simple devices like block, serial, and network types of devices.
FUSD. Seriously, closed source drivers running in kernel space are a bad idea. If companies want to release closed source drivers, and apparently they do since this whining about the lack of a fixed-forever ABI comes up every now and again, then those drivers should run in their own process space and not as part of the kernel.
That is a good point. However it might be worth considering having a hooks in the kernel to make interfacing to the user-space process easier. I think there is work on this going on and that is great. Low-bandwidth/high-latency devices will be able to move into userspace.
However I never want to see a video or audio driver running in userspace. I could be OK with a those drivers running in a "driver-space" if you will. Something like a microkernel. But userspace has way to high of latency and context switch costs.
I'm not sure what the solution is, but closed source drivers are not going to go away, so we will need a way to handle it. As crazy as it sounds maybe a microkernel type interface would be good. It would allow drivers to run outside the kernel without the cost of a full userspace context switch.
Wouldn't it be cool if a seeder could queue up lists of people who want a specific small hunk of a block and then send it out to all at once using multicast? It seems like that could actually have a pretty big band-width advantage over TCP. It would be hard to design. Since it would need to implement traffic shaping and all that, but I think it could actually produce a net reduction in bandwidth usage especially at the seed.
In fact it might be able to allow a single seed to appear to upload at many times its real bandwidth.
-Arthur
If you are converting biomass that would be well-sequestered, then you lose, but I tend to doubt that is a major problem, unless you tr to cut down a rain forest to get your biomass.
I would not put that past people.
That is exactly what I was getting at. But I didn't explain it well.
You're already carrying the sphere!