criu | MIO | |
---|---|---|
14 | 21 | |
2,663 | 6,087 | |
1.7% | 1.2% | |
8.9 | 8.4 | |
10 days ago | about 17 hours ago | |
C | Rust | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
criu
-
When "letting it crash" is not enough
Checkpoint/Restore I feel is a bigger concept than just saving state. At the zeroth level it's a system that can correctly stop and serialize a running process (as criu https://github.com/checkpoint-restore/criu has shown is a huge pain in the ass to still not be perfect) in a way that can initiated from within the process itself.
The 1st level more-work-but-easier way to do this is to build or use a heavily constrained VM/language you run from within your main application that doesn't allow for most of the hard problems to even exist.
I can't find any ready-made tools to do this that I wouldn't consider an endeavor.
- CRIU – Checkpoint/restore Linux tasks
-
Live Switching Pods to another Node on Resource Limits
That being said the Checkpoint Restore In Userspace project has been around for a number of years and is the closest thing to what you are talking about: taking a linux process on one machine and moving it to another. It is messy but can be done in some cases. There are folks looking at how to integrate CRIU with k8s but it’s all research at this point.
- Criu: Checkpoint/Restore Functionality for Linux
- checkpoint-restore/criu: Checkpoint/Restore tool
- checkpoint-restore/criu: Linux Checkpoint/Restore tool
-
The intersection of shadow stacks and CRIU
I would love to make more use of CRIU. E.g. I considered to use CRIU for my Python preloaded logic (https://github.com/albertz/python-preloaded). Unfortunately, at that point in time, CRIU must be used with root access, which was not an option. However, I see that the PR was merged now, so maybe it works now? (https://github.com/checkpoint-restore/criu/pull/1930)
There is also DMTCP (https://github.com/dmtcp/dmtcp/) but this might have other problems for my use case.
My solution was to use a fork server instead, which works almost equally well. There are not really much downsides with this approach. And this is actually quite simple, and also quite cross-platform (except Windows).
-
Python Preloaded
CRIU currently needs root access for dump/restore. However, there is ongoing work to support a non-root option in https://github.com/checkpoint-restore/criu/pull/1930.
-
How-to "freeze" a process to disk?
There have been multiple checkpointing attempts over the years. Criu is the only one I know of that's still kicking. That's probably your best and only bet.
- I made a plugin to suspend games and apps similar to how consoles do (Deck Suspender)
MIO
-
What's the canonical way of doing it in rust?
Was playing around with mio (https://github.com/tokio-rs/mio) (not that mio itself is very important here!) and was trying to implement a simple something that I've done in java before: a Reactor that you can register ReactorClients with that will get callback whenever there are events on the corresponding socket etc.
-
RFC: A non-blocking networking library for Rust
How does it compare to mio?
-
How does the Rust mio crate implement deregistering connections?
TcpStream gets its wake behavior by delegating to the fd wakers. The Unix wakers have a few implementations, for different platforms. On Linux and Android, epoll is used.
-
Looking for Tokio's event loop source code
The real implementation details of the I/O event queue is done in mio as u/hniksic pointed out, but that's more comparable with libuv which is certainly a huge part of the Node runtime. mio and libuv have a lot of similarities (at least they used to).
-
Python multi-level break and continue
My example was "twice by one developer", not "twice across all indexed repos."
A spot check shows that quite a few in your link are used specifically to ensure correct handling of Rust multi-level breaks work syntax, like https://github.com/rust-lang/rust-analyzer/blob/master/crate... , https://github.com/rust-lang/rustfmt/blob/master/tests/sourc... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... and likely more.
Another is a translation of BASIC code to Rust, using break as a form of goto. https://github.com/coding-horror/basic-computer-games/blob/e...
The example at https://github.com/tokio-rs/mio/blob/master/tests/tcp.rs is a nice one
// Wait for our TCP stream to connect
-
Crates to help with event-loop type pattern?
In my program, I have about 6 different components that follow the pattern below. Basically, the components run a thread while polling on crossbeam channels, file descriptors or sockets. For polling, I am using Mio (https://github.com/tokio-rs/mio).
-
Ask HN: Has any Rust developer moved to embedded device programming?
On the code side it's pretty much the same as C++. You have a module that defines an interface and per-platform implementations that are included depending on a "configuration conditional checks" #[cfg(target_os = "linux")] macro.
https://github.com/tokio-rs/mio/blob/c6b5f13adf67483d927b176...
- Mio - Metal io library for rust
-
`wasm32-wasi` support added to Tokio
Made possible by Wasi support for Mio https://github.com/tokio-rs/mio/pull/1576
-
What is the point of async and await?
Indeed! In practice it's done through the polling operation: instead of a separate poll for op1 and op2, the program essentially tells the OS "wake me when either op1 or op2 is ready" (through the epoll syscall on Linux). The mio crate implements this, and the example on the readme is basically the same loop, but written with this polling strategy in mind.
What are some alternatives?
nyrna - Suspend games and applications.
tokio
FitM - FitM, the Fuzzer in the Middle, can fuzz client and server binaries at the same time using userspace snapshot-fuzzing and network emulation. It's fast and comparably easy to set up.
rust-zmq - Rust zeromq bindings.
Regshot-Advanced - This is a fork of Regshot (original found at https://sourceforge.net/projects/regshot/) with very enhanced functionality.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
fpart - Sort files and pack them into partitions
glommio - Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
DashLoader - Launch at the speed of light.
actix - Actor framework for Rust.
nginx-link-function - It is a NGINX module that provides dynamic linking to your application in server context and call the function of your application in location directive
message-io - Fast and easy-to-use event-driven network library.