All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>, Bin Liu <b-liu@ti.com>,
	Johan Hovold <johan@kernel.org>
Subject: Re: am335x: performnce issues with FTDI and LOW_LATENCY
Date: Thu, 9 Mar 2023 09:30:00 +0200	[thread overview]
Message-ID: <20230309073000.GG7501@atomide.com> (raw)
In-Reply-To: <CAGm1_ktJH21qk=eRH_xJgwkf_pGCgp1z7Jrp5M2orZ-eNRNg=Q@mail.gmail.com>

* Yegor Yefremov <yegorslists@googlemail.com> [230307 09:53]:
> On Mon, Mar 6, 2023 at 8:42 AM Tony Lindgren <tony@atomide.com> wrote:
> >
> > * Yegor Yefremov <yegorslists@googlemail.com> [230228 08:01]:
> > > Any idea why the performance drop is so big?
> >
> > Maybe lots of interrupts and dma not being used for musb in this case?
> 
> Using "irqtop -d 1", I get the following results:
> 
> 3.18.1 LATENCY_OFF (16 ports): ca. 1000 IRQs/s INTC 17 47400000.dma-controller
> 3.18.1 LATENCY_ON (16 ports): ca. 4000 IRQs/s INTC 17 47400000.dma-controller
> 
> 6.2.1 LATENCY_OFF (16 ports): ca. 300 IRQs/s INTC 17 47400000.dma-controller
> 6.2.1 LATENCY_ON (16 ports): ca. 1000 IRQs/s INTC 17 47400000.dma-controller

Hmm I wonder what's causing that. Earlier the Ethernet gadget had some
alignment define tweak that made transfers faster. What kind of data
transfer are you testing with?

> #zcat /proc/config.gz | grep CPP
> CONFIG_USB_TI_CPPI41_DMA=y
> CONFIG_TI_CPPI41=y

From what I recall musb still handles short transfers with PIO, I think
this is the case also for cppi41 dma. Sounds like that does not explain
the difference you're seeing between 3.18 and 6.2 kernels though.

Regards,

Tony

  reply	other threads:[~2023-03-09  7:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  7:59 am335x: performnce issues with FTDI and LOW_LATENCY Yegor Yefremov
2023-03-06  7:42 ` Tony Lindgren
2023-03-07  9:53   ` Yegor Yefremov
2023-03-09  7:30     ` Tony Lindgren [this message]
2023-03-10 22:35       ` Bin Liu
2023-03-13  7:08         ` Yegor Yefremov
2023-03-23  7:06           ` Tony Lindgren

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=20230309073000.GG7501@atomide.com \
    --to=tony@atomide.com \
    --cc=b-liu@ti.com \
    --cc=johan@kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=yegorslists@googlemail.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 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.