Re: Futexes and network filesystems.

ardly more expensive the current >> getpid(). >> >> Once we have fixed the futex infrastructure to be able to handle futexes on >> network filesystems, the pid namespace case will be trivial to implement. > > Actually, I would think that get_vm_task_id(void *addr) would be a mor

Re: Futexes and network filesystems.

with potentially overlapping pid values this could be something else. It is an extra syscall in the preparation path, but it should be hardly more expensive the current getpid(). Once we have fixed the futex infrastructure to be able to handle futexes on network filesystems, the pid

Futexes and network filesystems.

rdly more expensive the current getpid(). Once we have fixed the futex infrastructure to be able to handle futexes on network filesystems, the pid namespace case will be trivial to implement. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Futexes and network filesystems.

contexts with potentially overlapping pid values this could be something else. It is an extra syscall in the preparation path, but it should be hardly more expensive the current getpid(). Once we have fixed the futex infrastructure to be able to handle futexes on network filesystems, the pid namespace

Re: Futexes and network filesystems.

with potentially overlapping pid values this could be something else. It is an extra syscall in the preparation path, but it should be hardly more expensive the current getpid(). Once we have fixed the futex infrastructure to be able to handle futexes on network filesystems, the pid

Re: Futexes and network filesystems.

on network filesystems, the pid namespace case will be trivial to implement. Actually, I would think that get_vm_task_id(void *addr) would be a more useful interface. The call would still be a relatively simple lookup to find the struct file associated with the particular virtual mapping