From: nick <xerofoify@gmail.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: tiwai@suse.de, axboe@kernel.dk, alsa-devel@alsa-project.org,
tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: Possible Bug Found with Xonar Stx Driver
Date: Fri, 10 Jul 2015 08:25:39 -0400 [thread overview]
Message-ID: <559FB9C3.2050108@gmail.com> (raw)
In-Reply-To: <559FB6F2.2000606@ladisch.de>
On 2015-07-10 08:13 AM, Clemens Ladisch wrote:
> nick wrote:
>> After running the latest version of Linus's tree I am noticed way more buffering
>
> What exactly do you mean with the word "buffering"?
>
>> when playing music with my Xonar STX card when building kernels then
>> under the Ubuntu kernel version of 3.19.16.
>
> Sounds like a change in the disk access patterns.
>
> The audio buffer size is chosen by the playing application (whatever it
> is).
>
>> I have tried bisecting it between the releases of 3.18 and 4.0
>> and was unable to narrow it down to a buggy commit.
>
> There was no relevant change in the sound driver.
>
>
> Regards,
> Clemens
>
I was looking just to see if there was just a direct commit that caused this not in the sound
driver but overall. Seems this is most likely either disk access issues or locking issues with
timeout related to refilling the audio buffer. In addition by buffering I mean the music halts
for a minute then continues when compiling the kernel. Further more I am also noticed my builds
are much fast upwards of 25% on the latest rc so a performance improvement in locking or better
disk access improvement may be a likely culprit. Ccing Ted and Jen as they are maintainers of
the file system I am using and Jen maintains the block layer.
Cheers,
Nick
prev parent reply other threads:[~2015-07-10 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <559EFC14.2090408@gmail.com>
2015-07-10 12:13 ` Possible Bug Found with Xonar Stx Driver Clemens Ladisch
2015-07-10 12:25 ` nick [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=559FB9C3.2050108@gmail.com \
--to=xerofoify@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=axboe@kernel.dk \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=tytso@mit.edu \
/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.