[[!meta copyright="Copyright © 2013, 2014 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!meta title="Interfaces"]] /!\ Incomplete. [[!map pages="microkernel/mach/gnumach/interface/*" show=title]] # Proposed ## Futex Add a futex kernel trap to GNU Mach. This can be useful for nicer locking primitives, including inter-process primitives. `vm_allocate` can be used as an example in the `gnumach` source tree for how to add a kernel trap. ### [[!GNU_Savannah_task 6231]] ### Patches on bug-hurd ### IRC, freenode, #hurd, 2014-01-20 braunr: i meant to ask about the futex stuff what do you mean when you talk about the interface ? i imagined something like this more precisely ? for shared futexes, do not use a pointer, but a right referencing a memory object, and the offset ? why not a pointer ? well, an address that's how it's currently done, right ? in marins prototype i mean yes it's a task/address pair so the only concern is the access in the kernel ? hum not only no or yes, but there are multiple ways to access i meant to say this, for me, it would be very helpful if you were more explicit when you describe how you picture something i thought i did it clearly i even agree with what roland describes which looks even clearer also, i said i didn't picture it completely :) i didn't want to work on that, only review sure, but what might be clear to you is most likely not that clear to me ok