From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Cc: Gabriel Krisman Bertazi <[email protected]>
Subject: Re: [PATCH liburing 1/1] examples: add rsrc update benchmark
Date: Tue, 04 Apr 2023 09:33:24 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <6914bc136c752f50fc8a818773a4cb61b5e39077.1680576220.git.asml.silence@gmail.com>
On Tue, 04 Apr 2023 13:37:39 +0100, Pavel Begunkov wrote:
> Add a stupid benchmark updating files in a loop mainly for profiling
> purposes and estimating the rsrc update overhead.
>
>
Applied, thanks!
[1/1] examples: add rsrc update benchmark
commit: c0940508607ff842d88344962eaa1bb5252d9ff3
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-04-04 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 12:37 [PATCH liburing 1/1] examples: add rsrc update benchmark Pavel Begunkov
2023-04-04 15:33 ` Jens Axboe [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=168062240489.178510.1631723061998732758.b4-ty@kernel.dk \
[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