1
0
Fork 0
forked from wry/wry

io: use io_uring for all io

There should no longer be any

- read
- write
- connect
- sendmsg
- recvmsg
- accept

calls in the codebase. Previously we were using a mix of io_uring and
these calls which had some negative effects: Since we were using the old
system calls, we had to set the file descriptors to non-blocking. But
our io_uring code did not handle EAGAIN. This lead to programs sometimes
being killed when the wayland IO was actually blocking.

Now all file descriptors are set to blocking, but io_uring makes it
non-blocking from our perspective. The one exception are evdev files
because they are read via libinput and libinput uses the old system
calls.
This commit is contained in:
Julian Orth 2022-12-31 17:55:58 +01:00
parent 2db0ee8995
commit 9812a02f87
55 changed files with 900 additions and 672 deletions

View file

@ -95,7 +95,7 @@ impl Clients {
&self,
id: ClientId,
global: &Rc<State>,
socket: OwnedFd,
socket: Rc<OwnedFd>,
secure: bool,
) -> Result<(), ClientError> {
let (uid, pid) = {
@ -123,7 +123,7 @@ impl Clients {
&self,
id: ClientId,
global: &Rc<State>,
socket: OwnedFd,
socket: Rc<OwnedFd>,
uid: c::uid_t,
pid: c::pid_t,
secure: bool,
@ -133,7 +133,7 @@ impl Clients {
id,
state: global.clone(),
checking_queue_size: Cell::new(false),
socket: Rc::new(socket),
socket,
objects: Objects::new(),
swapchain: Default::default(),
flush_request: Default::default(),