alan@redhat.com said:
> That really makes all the existing code not work with it.
Can you be more specific? If you're thinking I'm talking about breaking
mmap, munmap, and mprotect by adding another argument, I'm not. I'm talking
about adding new syscalls, mmap2, munmap2, mprotect2 (or something more
imaginative), which have the extra argument, having them take -1 as meaning
"fiddle the current address space" and pursuading libc to use them instead
of the current syscalls. Then we would start the current ones on their way
to the happy syscall hunting grounds in the sky.
> Doing an altmm is easy in the sense that it doesn't require 20 new
> syscall
I don't think I mentioned 20 new syscalls anywhere :-) If you count the
ones above as replacements and not new, I'm talking about one new syscall -
switch_mm(), which I didn't mention before, that would switch to a given
address space. This would be the basis of UML's switch_mm.
> and doesnt slow down the main kernel paths for a single odd
> case.
Which main kernel paths are you referring to here?
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:20 EST