From: Hao Xu <[email protected]>
To: Jens Axboe <[email protected]>, Pavel Begunkov <[email protected]>
Cc: [email protected], Joseph Qi <[email protected]>
Subject: Re: [PATCH] io_uring: add more uring info to fdinfo for debug
Date: Thu, 16 Sep 2021 14:29:45 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
在 2021/9/15 下午11:32, Jens Axboe 写道:
> On 9/15/21 9:31 AM, Pavel Begunkov wrote:
>> On 9/15/21 4:26 PM, Jens Axboe wrote:
>>> 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.
>>
>> Are there limits how much we can print? I remember people were couldn't
>> even show a list of CPUs (was it proc?). The overflow list may be huge.
>
> It's using seq_file, so I _think_ we should be fine here. Not sure when/if
> it truncates.
>
It seems the default buf size of seq_file is PAGE_SIZE.
prev parent reply other threads:[~2021-09-16 6:29 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
2021-09-15 15:31 ` Pavel Begunkov
2021-09-15 15:32 ` Jens Axboe
2021-09-16 6:29 ` Hao Xu [this message]
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=60bfddf8-d19a-102e-21dc-bf4ea7bf9724@linux.alibaba.com \
[email protected] \
[email protected] \
[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