From: Alexander Fomichev <fomichev.ru@gmail.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: ntb@lists.linux.dev, linux@yadro.com,
Jon Mason <jdmason@kudzu.us>, Allen Hubbe <allenbh@gmail.com>,
Yang Li <yang.lee@linux.alibaba.com>,
Serge Semin <fancer.lancer@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ntb_perf: extend with burst/poll/doorbell latency measurement
Date: Tue, 19 Apr 2022 00:11:13 +0300 [thread overview]
Message-ID: <20220418211113.oxidrif4jtjlqr2r@yadro.com> (raw)
In-Reply-To: <9ad57247-36df-cb3d-d50f-feb3c80f17e6@intel.com>
On Mon, Apr 18, 2022 at 07:52:50AM -0700, Dave Jiang wrote:
>
> I don't see any major issues with the code. However, is it possible to break
> the introduction of these 3 metrics into 3 different patches for easier
> review?
>
Sure. I'll re-post the separate patches soon.
--
Regards,
Alexander
prev parent reply other threads:[~2022-04-18 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 23:55 [PATCH] ntb_perf: extend with burst/poll/doorbell latency measurement Alexander Fomichev
2022-04-18 14:52 ` Dave Jiang
2022-04-18 21:11 ` Alexander Fomichev [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=20220418211113.oxidrif4jtjlqr2r@yadro.com \
--to=fomichev.ru@gmail.com \
--cc=allenbh@gmail.com \
--cc=dave.jiang@intel.com \
--cc=fancer.lancer@gmail.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@yadro.com \
--cc=ntb@lists.linux.dev \
--cc=yang.lee@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 read-only IMAP folder(s) and NNTP newsgroup(s).