[EMAIL PROTECTED] wrote:
> This sounds like it would be possible. Another idea a colleague at work
> suggested was to make everyone share the same virtual address mappings,
> i.e. you don't have to flush the cache on a context switch. There would
> be one set of virtual mappings that everyone gets mapped to.
I don't get you; how does this differ from what we have at the moment?
Everything gets mapped to one address...
> Of course, another option (an idea even more hated than Neals, I'm
> guessing:) would be to make Linux be able to handle a flat address
> space. Then you can use the MMU for protection only, and have two sets
> of page tables, one for the kernel, and one for everyone else. User
> processes can then splat each other, but not the kernel. This makes the
> system somewhat more functional than MS-DOS or MAC-OS.:) Not a popular
> option, but for some occasions, this might be nice. (i.e. embedded
> systems running Linux).
This makes sense, but what makes even more sense is to run with a proper
CPU for the target :-) Running multi-user UNIX systems on things like
strongarms is, IMHO, scaling them up too much if they are used in a
scalable (ie non-UI or something like web serving) context.
Why not just use an SH-4 or something?
Neil
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
