From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET 0/2] eventfd handling cleanups
Date: Mon, 3 Jun 2024 12:03:16 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
Patch 1 I ran into while doing other work, causing leaks. As far as I
can tell, not triggerable in the current tree, but I do think the
rewritten handling of eventfd is much better and more closely follows
the expected RCU usage.
Patch 2 is just a cleanup on top. There's no reason to keep the eventfd
code in both io_uring.c and register.c, move it to a separate file to
avoid polluting the global space.
--
Jens Axboe
next reply other threads:[~2024-06-03 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 18:03 Jens Axboe [this message]
2024-06-03 18:03 ` [PATCH 1/2] io_uring/eventfd: move to more idiomatic RCU free usage Jens Axboe
2024-06-03 18:03 ` [PATCH 2/2] io_uring/eventfd: move eventfd handling to separate file Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox