RE: [Lse-tech] [rfc][api] Shared Memory Binding

[Luck, T. <ton...@in...>]

> 	I've got a pseudo manpage for a new call I'm attempting=20
> to implement:=20
> shmbind().  The idea of the call is to allow userspace=20
> processes to bind=20
> shared memory segments to particular nodes' memory and do so=20
> according=20
> to certain policies.  Processes would call shmget() as usual,=20
> but before=20
> calling shmat(), the process could call shmbind() to set up a binding=20
> for the segment.  Then, any time pages from the shared segment are=20
> faulted into memory, it would be done according to this binding.
> 	Any comments about the attatched manpage, the idea in=20
> general, how to improve it, etc. are definitely welcome.

Why tie this to the sysV ipc shm mechanism?  Couldn't you make
a more general "mmbind()" call that applies to a "start, len"
range of virtual addresses?  This would work for your current
usage (but you would apply it after the "shmat()"), but it would
also be useful for memory allocated to a process with mmap(), sbrk()
and even general .text/.data if you managed to call it before you
touched pages.

-Tony