From: Stefan Roesch <shr@fb.com>
To: <io-uring@vger.kernel.org>, <kernel-team@fb.com>
Cc: <shr@fb.com>
Subject: [PATCH v1 0/2] io-uring: use consisten tracepoint format
Date: Mon, 14 Feb 2022 10:04:28 -0800 [thread overview]
Message-ID: <20220214180430.70572-1-shr@fb.com> (raw)
So far the tracepoints haven't used a consistent format. This change
adds consistent formatting for the io-uring tracepoints. This makes it
easier to follow individual requests.
Where it makes sense it uses the following format:
- context structure pointer
- request structure pointer
- user data
- opcode.
Stefan Roesch (2):
io-uring: add __fill_cqe function
io-uring: Make tracepoints consistent.
fs/io_uring.c | 42 +++--
include/trace/events/io_uring.h | 320 +++++++++++++++-----------------
2 files changed, 178 insertions(+), 184 deletions(-)
base-commit: 754e0b0e35608ed5206d6a67a791563c631cec07
--
2.30.2
next reply other threads:[~2022-02-14 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 18:04 Stefan Roesch [this message]
2022-02-14 18:04 ` [PATCH v1 1/2] io-uring: add __fill_cqe function Stefan Roesch
2022-02-14 18:04 ` [PATCH v1 2/2] io-uring: Make tracepoints consistent Stefan Roesch
2022-02-15 21:28 ` [PATCH v1 0/2] io-uring: use consisten tracepoint format 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=20220214180430.70572-1-shr@fb.com \
--to=shr@fb.com \
--cc=io-uring@vger.kernel.org \
--cc=kernel-team@fb.com \
/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