From: Dmitry Dolgov <9erthalion6@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Subject: Re: [RFC v1] io_uring: add io_uring_link trace event
Date: Tue, 8 Oct 2019 15:11:01 +0200 [thread overview]
Message-ID: <CA+q6zcWqWAWG7UqzOekEH71XGUb24WpmJqe9juK94C4wq=1xsw@mail.gmail.com> (raw)
In-Reply-To: <b86e5648-9464-1f1a-0faa-15b489fda26a@kernel.dk>
> On Tue, Oct 8, 2019 at 3:02 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> > If I'm missing something and it doesn't make sense, then I would be
> > glad to hear if there are any best practices or ideas, and in general
> > how to look at io_uring from the tracing point of view.
>
> I think it makes sense, and in fact I'd encourage you to expand the
> tracing so we can get better insight into io_uring doing what it should
> be doing.
Sure. I was investigating this topic for some time, and hopefully soon I can
prepare a patch with more intensive tracing for most important aspects.
prev parent reply other threads:[~2019-10-08 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 12:53 [RFC v1] io_uring: add io_uring_link trace event Dmitrii Dolgov
2019-10-08 12:54 ` Dmitry Dolgov
2019-10-08 13:01 ` Jens Axboe
2019-10-08 13:11 ` Dmitry Dolgov [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='CA+q6zcWqWAWG7UqzOekEH71XGUb24WpmJqe9juK94C4wq=1xsw@mail.gmail.com' \
--to=9erthalion6@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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 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).