From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
Florian-Ewald Mueller <florian-ewald.mueller@cloud.ionos.com>
Subject: Re: [PATCH RFC 4/5] block: add a statistic table for io latency
Date: Thu, 9 Jul 2020 20:48:08 +0200 [thread overview]
Message-ID: <cc04e449-3d41-3ef7-10c2-c257512d7650@cloud.ionos.com> (raw)
In-Reply-To: <b37dd9cd-aebc-88ee-2b09-ac4eb36ca0f7@cloud.ionos.com>
Hi Ming,
On 7/8/20 4:06 PM, Guoqing Jiang wrote:
> On 7/8/20 4:02 PM, Guoqing Jiang wrote:
>>> Hi Guoqing,
>>>
>>> I believe it isn't hard to write a ebpf based script(bcc or
>>> bpftrace) to
>>> collect this kind of performance data, so looks not necessary to do it
>>> in kernel.
>>
>> Hi Ming,
>>
>> Sorry, I don't know well about bcc or bpftrace, but I assume they
>> need to
>> read the latency value from somewhere inside kernel. Could you point
>> how can I get the latency value? Thanks in advance!
>
> Hmm, I suppose biolatency is suitable for track latency, will look
> into it.
I think biolatency can't trace data if it is not running, also seems no
place
inside kernel have recorded such information for ebpf to read, correct me
if my understanding is wrong.
And as cloud provider,we would like to know data when necessary instead
of collect data by keep script running because it is expensive than just
read
node IMHO.
Thanks,
Guoqing
next prev parent reply other threads:[~2020-07-09 18:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 7:58 [RFC PATCH 0/4] block: add two statistic tables Guoqing Jiang
2020-07-08 7:58 ` [PATCH RFC 1/5] block: return ns precision from disk_start_io_acct Guoqing Jiang
2020-07-08 13:27 ` Ming Lei
2020-07-08 13:53 ` Guoqing Jiang
2020-07-08 17:46 ` Guoqing Jiang
2020-07-08 7:58 ` [PATCH RFC 2/5] drbd: remove unused argument from drbd_request_prepare and __drbd_make_request Guoqing Jiang
2020-07-08 7:58 ` [PATCH RFC 3/5] drbd: rename start_jif to start_ns Guoqing Jiang
2020-07-08 7:58 ` [PATCH RFC 4/5] block: add a statistic table for io latency Guoqing Jiang
2020-07-08 13:29 ` Ming Lei
2020-07-08 14:02 ` Guoqing Jiang
2020-07-08 14:06 ` Guoqing Jiang
2020-07-09 18:48 ` Guoqing Jiang [this message]
2020-07-10 0:53 ` Ming Lei
2020-07-10 8:55 ` Guoqing Jiang
2020-07-10 10:00 ` Ming Lei
2020-07-10 10:29 ` Guoqing Jiang
2020-07-11 1:32 ` Ming Lei
2020-07-12 20:39 ` Guoqing Jiang
2020-07-12 20:44 ` Jens Axboe
2020-07-12 21:04 ` Guoqing Jiang
2020-07-10 14:04 ` Jens Axboe
2020-07-08 7:58 ` [PATCH RFC 5/5] block: add a statistic table for io sector Guoqing Jiang
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=cc04e449-3d41-3ef7-10c2-c257512d7650@cloud.ionos.com \
--to=guoqing.jiang@cloud.ionos.com \
--cc=axboe@kernel.dk \
--cc=florian-ewald.mueller@cloud.ionos.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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