[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220421091345.2115755-3-dylany@fb.com>
Date: Thu, 21 Apr 2022 02:13:41 -0700
From: Dylan Yudaken <dylany@...com>
To: <io-uring@...r.kernel.org>
CC: <axboe@...nel.dk>, <asml.silence@...il.com>,
<linux-kernel@...r.kernel.org>, <kernel-team@...com>,
Dylan Yudaken <dylany@...com>
Subject: [PATCH 2/6] io_uring: trace cqe overflows
Trace cqe overflows in io_uring. Print ocqe before the check, so if it is
NULL it indicates that it has been dropped.
Signed-off-by: Dylan Yudaken <dylany@...com>
---
fs/io_uring.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/io_uring.c b/fs/io_uring.c
index 7e1d5243bbbc..d654faffa486 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -2107,6 +2107,7 @@ static bool io_cqring_event_overflow(struct io_ring_ctx *ctx, u64 user_data,
struct io_overflow_cqe *ocqe;
ocqe = kmalloc(sizeof(*ocqe), GFP_ATOMIC | __GFP_ACCOUNT);
+ trace_io_uring_cqe_overflow(ctx, user_data, res, cflags, ocqe);
if (!ocqe) {
/*
* If we're in ring overflow flush mode, or in task cancel mode,
--
2.30.2
Powered by blists - more mailing lists