WIP: Add support for mbind, get_mempolicy and set_mempolicy
#938
Conversation
…ealliance#938) This adds support for the `mbind`, `set_mempolicy` and `get_mempolicy` NUMA syscalls. The `get_mempolicy` syscall has a few different modes of operation, depending on the flags, which is demultiplexed into `get_mempolicy_node` and `get_mempolicy_next_node` for now. There's a couple of other modes that writes into the variable length bit array, which aren't implemented for now.
krh
force-pushed
the
numa
branch
2 times, most recently
from
6fe1aa4 to
f321b15
Compare
tests/numa/mbind.rs~
Outdated
| rustix::fs::seek(&alt, rustix::fs::SeekFrom::Current(0)), | ||
| Ok(12) | ||
| ); | ||
| } |
There was a problem hiding this comment.
Are mbind.rs~ and main.rs~ editor backups?
There was a problem hiding this comment.
Yes, oops, that's emacs backup files.
krh
force-pushed
the
numa
branch
3 times, most recently
from
097eae4 to
49a7171
Compare
|
Pushed a new version: removed the emacs backup files, fixed |
|
This one: sunfishcode/linux-raw-sys#96 |
krh
force-pushed
the
numa
branch
2 times, most recently
from
52f2271 to
4c5f6ce
Compare
|
If you'd like this PR to be included in the rustix 0.38 series, please use linux-raw-sys 0.4.x. I've now released 0.4.12 with sunfishcode/linux-raw-sys#96. Another option is to open this PR in the 1.0-staging branch. |
Oh, ok, thanks, I'll target 0.4.12 then. |
…ealliance#937) This adds support for the `mbind`, `set_mempolicy` and `get_mempolicy` NUMA syscalls. The `get_mempolicy` syscall has a few different modes of operation, depending on the flags, which is demultiplexed into `get_mempolicy_node` and `get_mempolicy_next_node` for now. There's a couple of other modes that writes into the variable length bit array, which aren't implemented for now.
|
Rustix 1.0.0 is now released, and it uses the latest linux-raw-sys, so it's no longer necessary to backport to linux-raw-sys 0.4. |
2 participants
This adds support for the
mbind,set_mempolicyandget_mempolicyNUMA syscalls. Theget_mempolicysyscall has a few different modes of operation, depending on the flags, which is demultiplexed intoget_mempolicy_nodeandget_mempolicy_next_nodefor now. There's a couple of other modes that writes into the variable length bit array, which aren't implemented for now.