From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Thomas.Kopp@microchip.com
Cc: linux-can@vger.kernel.org, kernel@pengutronix.de,
manivannan.sadhasivam@linaro.org
Subject: Re: can-next 2022-03-13: mcp251xfd: add
Date: Wed, 23 Mar 2022 20:28:58 +0100 [thread overview]
Message-ID: <20220323192858.pixhyf2jzah7eqiv@pengutronix.de> (raw)
In-Reply-To: <DM4PR11MB5390224F4ABAED6DFC430266FB189@DM4PR11MB5390.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On 23.03.2022 15:00:31, Thomas.Kopp@microchip.com wrote:
> > For better reproducibility I set the scaling_governor to performance:
> >
> > | echo performance | sudo tee
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
> >
> > I've no idea why an unpachted v5.17 generates more SPI IRQs.
> >
> > Can you re-test with performance mode activated, I'm not sure when I
> > find time to look into this.
> >
> Yes, will do. For the record, the difference was really marginal. On
> 20k frames I had 39182 vs. 39139 SPI interrupts.
I assume in some case the RX processing took so long that there was
another RX CAN frame ready in the same IRQ handler run.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-23 19:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 8:36 can-next 2022-03-13: mcp251xfd: add Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 01/12] can: mcp251xfd: mcp251xfd_ring_init(): use %d to print free RAM Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 02/12] can: mcp251xfd: ram: add helper function for runtime ring size calculation Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 03/12] can: mcp251xfd: ram: coalescing support Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 04/12] can: mcp251xfd: ethtool: add support Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 05/12] can: mcp251xfd: ring: prepare support for runtime configurable RX/TX ring parameters Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 06/12] can: mcp251xfd: update macros describing ring, FIFO and RAM layout Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 07/12] can: mcp251xfd: ring: add support for runtime configurable RX/TX ring parameters Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 08/12] can: mcp251xfd: add RX IRQ coalescing support Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 09/12] can: mcp251xfd: add RX IRQ coalescing ethtool support Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 10/12] can: mcp251xfd: add TX IRQ coalesce support Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 11/12] can: mcp251xfd: add TX IRQ coalesce ethtool support Marc Kleine-Budde
2022-03-13 8:36 ` [can-next-rfc 12/12] can: mcp251xfd: ring: increase number of RX-FIFOs to 3 and increase max TX-FIFO depth to 16 Marc Kleine-Budde
2022-03-23 13:28 ` can-next 2022-03-13: mcp251xfd: add Thomas.Kopp
2022-03-23 14:03 ` Marc Kleine-Budde
2022-03-23 15:00 ` Thomas.Kopp
2022-03-23 19:28 ` Marc Kleine-Budde [this message]
2022-03-24 12:28 ` Thomas.Kopp
2022-03-24 13:45 ` can-next 2022-03-13: mcp251xfd: add coalescing support Marc Kleine-Budde
2022-03-29 9:08 ` can-next 2022-03-13: mcp251xfd: add Thomas.Kopp
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=20220323192858.pixhyf2jzah7eqiv@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=Thomas.Kopp@microchip.com \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.