All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	lgirdwood@gmail.com, broonie@kernel.org
Cc: linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
	yung-chuan.liao@linux.intel.com, yuhsuan@google.com
Subject: Re: [PATCH] ASoC: SOF: Use high-priority workqueue for PCM period elapsed
Date: Fri, 31 Jul 2026 11:20:08 +0200	[thread overview]
Message-ID: <c1ed5264-9a03-4436-b17c-8c1f59289b5e@linux.dev> (raw)
In-Reply-To: <20260730130445.8277-1-peter.ujfalusi@linux.intel.com>

On 7/30/26 15:04, Peter Ujfalusi wrote:
> From: Yu-Hsuan Hsu <yuhsuan@google.com>
> 
> The snd_sof_pcm_period_elapsed function currently schedules work on the
> system-wide workqueue. This can lead to potential delays or jitter in
> audio processing if the system workqueue is busy with other tasks.
> 
> To improve real-time performance and ensure timely processing of PCM
> periods, we can use the system_highpri_wq instead of the default work
> queue.
> 
> In performance testing, this change significantly reduced the observed
> scheduling delays. For instance, under load(stressapptest -M 15000 -m
> 60), the maximum delay dropped from 9ms on the system workqueue to 5ms
> on the dedicated high-priority workqueue.
> 
> Suggested-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Signed-off-by: Yu-Hsuan Hsu <yuhsuan@google.com>
> Reviewed-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
> Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Reviewed-by: Bard Liao <yung-chuan.liao@linux.intel.com>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>

Sounds good but should this higher priority queue be used for other
things as well?

e.g.

period-elapsed for compressed streams:
schedule_work(&spcm->stream[cstream->direction].period_elapsed_work);

and the SoundWire interrupt handling with additional workqueues:
schedule_work(&amd_manager->amd_sdw_irq_thread);
schedule_work(&amd_manager->amd_sdw_work);
schedule_work(&cdns->work);

Not sure what the rules are to define what's high-priority and what's
not... It could be that different systems have different requirements...

> ---
>  sound/soc/sof/pcm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/sound/soc/sof/pcm.c b/sound/soc/sof/pcm.c
> index b2071edeaea6..f748d072109a 100644
> --- a/sound/soc/sof/pcm.c
> +++ b/sound/soc/sof/pcm.c
> @@ -62,7 +62,7 @@ void snd_sof_pcm_period_elapsed(struct snd_pcm_substream *substream)
>  	 * To avoid sending IPC before the previous IPC is handled, we
>  	 * schedule delayed work here to call the snd_pcm_period_elapsed().
>  	 */
> -	schedule_work(&spcm->stream[substream->stream].period_elapsed_work);
> +	queue_work(system_highpri_wq, &spcm->stream[substream->stream].period_elapsed_work);
>  }
>  EXPORT_SYMBOL(snd_sof_pcm_period_elapsed);
>  


  reply	other threads:[~2026-07-31  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 13:04 [PATCH] ASoC: SOF: Use high-priority workqueue for PCM period elapsed Peter Ujfalusi
2026-07-31  9:20 ` Pierre-Louis Bossart [this message]
2026-07-31  9:31   ` Péter Ujfalusi
2026-07-31 12:19     ` Pierre-Louis Bossart
2026-07-31 13:04       ` Péter Ujfalusi

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=c1ed5264-9a03-4436-b17c-8c1f59289b5e@linux.dev \
    --to=pierre-louis.bossart@linux.dev \
    --cc=broonie@kernel.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=yuhsuan@google.com \
    --cc=yung-chuan.liao@linux.intel.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.