From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, asml.silence@gmail.com
Subject: [PATCH for-next 0/3] io_uring trace events clean up
Date: Thu, 16 Jun 2022 13:57:17 +0100 [thread overview]
Message-ID: <cover.1655384063.git.asml.silence@gmail.com> (raw)
Make io_uring_types.h public and teach tracing how to derive
opcode, user_data, etc. from io_kiocb.
note: rebased on top of the hashing patches
Pavel Begunkov (3):
io_uring: kill extra io_uring_types.h includes
io_uring: make io_uring_types.h public
io_uring: clean up tracing events
{io_uring => include/linux}/io_uring_types.h | 28 ++++-
include/trace/events/io_uring.h | 118 +++++++------------
io_uring/advise.c | 1 -
io_uring/cancel.c | 1 -
io_uring/epoll.c | 1 -
io_uring/fdinfo.c | 1 -
io_uring/filetable.c | 1 -
io_uring/filetable.h | 11 --
io_uring/fs.c | 1 -
io_uring/io-wq.h | 17 +--
io_uring/io_uring.c | 17 +--
io_uring/io_uring.h | 4 +-
io_uring/kbuf.c | 1 -
io_uring/msg_ring.c | 1 -
io_uring/net.c | 1 -
io_uring/nop.c | 1 -
io_uring/opdef.c | 1 -
io_uring/openclose.c | 1 -
io_uring/poll.c | 6 +-
io_uring/refs.h | 2 +-
io_uring/rsrc.c | 1 -
io_uring/rw.c | 1 -
io_uring/splice.c | 1 -
io_uring/sqpoll.c | 1 -
io_uring/statx.c | 1 -
io_uring/sync.c | 1 -
io_uring/tctx.c | 1 -
io_uring/timeout.c | 4 +-
io_uring/uring_cmd.c | 1 -
io_uring/xattr.c | 1 -
30 files changed, 85 insertions(+), 143 deletions(-)
rename {io_uring => include/linux}/io_uring_types.h (96%)
--
2.36.1
next reply other threads:[~2022-06-16 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 12:57 Pavel Begunkov [this message]
2022-06-16 12:57 ` [PATCH for-next 1/3] io_uring: kill extra io_uring_types.h includes Pavel Begunkov
2022-06-16 12:57 ` [PATCH for-next 2/3] io_uring: make io_uring_types.h public Pavel Begunkov
2022-06-16 12:57 ` [PATCH for-next 3/3] io_uring: clean up tracing events Pavel Begunkov
2022-06-17 13:35 ` [PATCH for-next 0/3] io_uring trace events clean up 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 \
--in-reply-to=cover.1655384063.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.