From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Théo Lebrun" <theo.lebrun@bootlin.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dhruva Gole" <d-gole@ti.com>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Tawfik Bayouk" <tawfik.bayouk@mobileye.com>
Subject: Re: [PATCH] spi: spi-mem: add statistics support to ->exec_op() calls
Date: Wed, 14 Feb 2024 07:42:57 +0000 [thread overview]
Message-ID: <d5d71068-eff7-4a1d-ad2f-948bf0313b9c@linaro.org> (raw)
In-Reply-To: <69f023bb-2844-496f-9f3f-4e2e80129d33@sirena.org.uk>
On 2/13/24 15:28, Mark Brown wrote:
> On Tue, Feb 13, 2024 at 12:39:02PM +0000, Tudor Ambarus wrote:
>> On 2/9/24 13:51, Théo Lebrun wrote:
>
>>> + if (!ret || ret != -ENOTSUPP || ret != -EOPNOTSUPP) {
>>> + spi_mem_add_op_stats(ctlr->pcpu_statistics, op, ret);
>>> + spi_mem_add_op_stats(mem->spi->pcpu_statistics, op, ret);
>>> +
>
>> Would be good to be able to opt out the statistics if one wants it.
>
>> SPI NORs can write with a single write op maximum page_size bytes, which
>> is typically 256 bytes. And since there are SPI NORs that can run at 400
>> MHz, I guess some performance penalty shouldn't be excluded.
>
> If we can cope with this sort of statistics collection in the networking
> fast path we can probably cope with it for SPI too, the immediate
> recording is all per CPU so I'd like to see some numbers showing that
> it's a problem before worrying about it too much. Even the people doing
> things like saturating CAN buses haven't been raising it as a concern
> for the regular SPI data path. We could add a Kconfig if it's an issue.
Ok, we can deal with it afterwards if it'll become an issue.
prev parent reply other threads:[~2024-02-14 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 13:51 [PATCH] spi: spi-mem: add statistics support to ->exec_op() calls Théo Lebrun
2024-02-12 11:13 ` Dhruva Gole
2024-02-12 13:35 ` Mark Brown
2024-02-12 14:22 ` Théo Lebrun
2024-02-13 4:54 ` Dhruva Gole
2024-02-13 12:39 ` Tudor Ambarus
2024-02-13 15:00 ` Théo Lebrun
2024-02-14 8:00 ` Tudor Ambarus
2024-02-14 8:51 ` Théo Lebrun
2024-02-14 9:29 ` Tudor Ambarus
2024-02-14 10:59 ` Théo Lebrun
2024-02-14 12:59 ` Tudor Ambarus
2024-02-13 15:28 ` Mark Brown
2024-02-14 7:42 ` Tudor Ambarus [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=d5d71068-eff7-4a1d-ad2f-948bf0313b9c@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=broonie@kernel.org \
--cc=d-gole@ti.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tawfik.bayouk@mobileye.com \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.kondratiev@mobileye.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 NNTP newsgroup(s).