Re: My Vintage Dream PC

???

Could you kindly cite a reputable publication that uses a spelling other than "kernel"?

NB this doesn't count:

PS "linux kernal" => "about 42,100" Google hits "linux kernel" => "about 11,800,00" Google hits

for a Richoux ratio in excess of 280:1.

Well, for one thing, whenever they have set a goal of doing some non-human- style thinking, and reached the goal successfully, someone has moved the goal posts and declared that it wasn't artificial intelligence.

For another thing, if you want to understand how something is done, try teaching a machine to do it. Lots of people are interested in how thinking is done.

My sense is that it's spelled both ways in the same alternate universe in which microkernels are a new concept.

I see.

Rule of thumb: Never form conclusions based on a conversation that begins (or is seen, as the conversations progresses, to have ought to have begun) with "What color is the sky where you are?".

There *are* currently some applications that require a lot of power. (Think of Photoshop...) When more horsepower or memory is available,

Twenty years ago it was *not* practical to store videos and large digital photos on your personal computer. The expanded memory, faster CPU's, and larger hard disks make it practical today.

That beco,es a problem when you do not respond to the right post. You responded to the troll's post, where he was attacking me.

Buzz off, ya little punk. The discussion is about time management and such. Knowing that, you comment becomes invalid. If you think it remains valid, then you are the one that is buzzword happy.

We should call Cardinal Richouxlou. :-)

So all CPUs will spend their idle time sniffing this common memory? Is this memory extensible so that, when it's full, the memory block can be expanded? If it's expanded, who does the expansion? When it's expanded, how do the other CPUs detect that the block is no longer the size it used to be? And where will that block be located? Moving it around would cause grey hairs to grow on the bit gods.

It can't be fixed. If a new piece of data is needed in future implementations, the area has to be able to expand and contract.

Whose hardware register?

This sounds like the common memory is far away from each CPU which means a latency of updating data. So there has to be a mechanism that tells other CPUs that one of them is writing a piece of data. If two CPUs are writing the same piece, who wins? If one is writing while another is reading the same piece of data, which bits are the "real" data? And how to the two (or 3 or 4 or...n) decide which data is the "right" data? Note that the last write does not necessarily have to be the correct data.

Can you think of any scenarios where this timer has to have a higher priority than the read/write to the common memory of the system?

that's not soon enough.

Exactly. think about that.

Yep which is why a master/slave concept cannot work well for any general timesharing. I suppose a dedicated system (where one, and only one, thing is done may be able to work but that has a completely different set of problems.

Even if the CPU runs faster than the speed of light but it still cannot cooperate if all the other CPUs match its speed. If there is a slower mechanism in the mix, all fast CPUs will be waiting for it to "catch up". this goes back to problem of having n CPUs in cpu-wait before they can execute their assigned tasks.

/BAH

Nuts. [that was said politely :-)] Consider a system that has an uptime of years. Rebooting to acquire or redistribute resources is not an option. think about replacing or adding gear without having to reload the system. And what about cores who have a need to cooperate with each other? Then think about updating software such as those DLLs (I think that's what you call them). Are you going to cause a system or CPU reboot? If you do need a CPU to reboot, how do you go about it without having to take the rest of the CPUs or the whole system down?

And this is just thinking about executables which are staid; I'm not thinking at all about data, static nor variable. Good grief...the static data would be a bitch...now that I am thinking about it.

And the 1990s were mostly small computer thinking. Some days, I wish the distributed computing had stayed a pipe dream in the 80s.

/BAH

It's worse than that. They aren't teaching that computing cannot break the laws of physics. c is slow.

/BAH

Obviously :-).

Sigh! I think I need to find my virtual baseball bat.

/BAH

That wasn't often enough in the auld days. What makes you think that it will suffice now?

I no longer know how to explain to you.

Man! You are way ahead of design.

/BAH

Huh? Separating the data from the code was riskier? How?

/BAH

Now think about having a system that can fetch tons of data just before you need it...especially this GUI crap...or movies or music or anything that has lots bytes.

/BAH

/BAH

If you want to understand how something is done, have a person who does the work teach you. The problem with these "AI" snobs (and these are not the people who are really doing AI work) is that they assume they are the experts and have no time nor respect for the people who actually can do the work well.

/BAH

Wet :-(((.

/BAH

Why? Do you expect your ass to explode before your head? Understandably, your ass could easily be mistaken for your head - and vice versa.