From: Takashi Iwai <tiwai@suse.de>
To: "Cássio Gabriel" <cassiogabrielcontato@gmail.com>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound: oss: dmasound: kick queued output before extending tail fragment
Date: Wed, 29 Apr 2026 07:53:28 +0200 [thread overview]
Message-ID: <87zf2mpb1j.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260427-dmasound-sq-play-v1-1-28bbeb8509b1@gmail.com>
On Tue, 28 Apr 2026 00:13:28 +0200,
Cássio Gabriel wrote:
>
> sq_write() currently clears POST and then immediately appends
> to the current rear fragment.
>
> If the queue already contains complete fragments ahead of that
> incomplete tail, playback is not kicked until the queue-full wait
> path or the final sq_play() at the end of the write. That wastes
> the slack those queued samples would otherwise provide while the driver
> spends more time copying and translating more data into the tail fragment.
>
> All in-tree dmasound playback backends still refuse to queue
> an incomplete last fragment while !syncing, but they can start
> earlier complete fragments.
>
> Call sq_play() immediately after clearing POST and before extending
> the rear fragment so already-queued complete output can start earlier.
>
> Signed-off-by: Cássio Gabriel <cassiogabrielcontato@gmail.com>
Applied to for-next branch now. Thanks.
Takashi
prev parent reply other threads:[~2026-04-29 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 22:13 [PATCH] sound: oss: dmasound: kick queued output before extending tail fragment Cássio Gabriel
2026-04-29 5:53 ` Takashi Iwai [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=87zf2mpb1j.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=cassiogabrielcontato@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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