From: Jens Axboe <axboe@kernel.dk>
To: Hao Xu <haoxu@linux.alibaba.com>
Cc: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>,
Joseph Qi <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH] io_uring: add more uring info to fdinfo for debug
Date: Wed, 15 Sep 2021 09:26:37 -0600 [thread overview]
Message-ID: <3ecf6b05-e92d-7d74-8f72-983ec0d790fc@kernel.dk> (raw)
In-Reply-To: <20210913130854.38542-1-haoxu@linux.alibaba.com>
On 9/13/21 7:08 AM, Hao Xu wrote:
> Developers may need some uring info to help themselves debug and address
> issues, these info includes sqring/cqring head/tail and the detail
> sqe/cqe info, which is very useful when it stucks.
I think this is a good addition, more info to help you debug a stuck case
is always good. I'll queue this up for 5.16.
--
Jens Axboe
next prev parent reply other threads:[~2021-09-15 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 13:08 [PATCH] io_uring: add more uring info to fdinfo for debug Hao Xu
2021-09-15 13:01 ` Hao Xu
2021-09-15 15:26 ` Jens Axboe [this message]
2021-09-15 15:31 ` Pavel Begunkov
2021-09-15 15:32 ` Jens Axboe
2021-09-16 6:29 ` Hao Xu
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=3ecf6b05-e92d-7d74-8f72-983ec0d790fc@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=haoxu@linux.alibaba.com \
--cc=io-uring@vger.kernel.org \
--cc=joseph.qi@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).