public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	linux-sound@vger.kernel.org
Subject: Re: regression/bisected/6.9 commit 587d67fd929ad89801bcc429675bda90d53f6592 decrease 30% of gaming performance
Date: Mon, 01 Apr 2024 13:41:45 +0200	[thread overview]
Message-ID: <87v851e2di.wl-tiwai@suse.de> (raw)
In-Reply-To: <CABXGCsMmRFW3EYJ3UvNd-LO7ZTOyoNqjc_3OAmaCDSL=LuxJqg@mail.gmail.com>

On Mon, 01 Apr 2024 13:07:26 +0200,
Mikhail Gavrilov wrote:
> 
> On Mon, Apr 1, 2024 at 12:07 PM Takashi Iwai <tiwai@suse.de> wrote:
> >
> > Is it a regression against the performance on 6.8?
> >
> > If so, what happens when you revert both this (587d67fd929a) and
> > beb45974dd49?  That should make the timer code back to 6.8 code.
> >
> >
> > Takashi
> 
> The commit beb45974dd49 boosted performance to 30%, but commit
> 587d67fd929a canceled this boost.
> 
> I want to say that reverting commit beb45974dd49 returns performance
> to 83FPS [1] and this is sad.
> 
> So I ask again is it possible to find a better approach than 587d67fd929a?
> 
> [1] https://postimg.cc/xJMjkcHP

The only code of the commit 587d67fd929a is the close of ALSA timer
device.  If it really matters, it implies that the user-space seems
trying to open/close the ALSA timer device so frequently.

Are you using ALSA dmix/dsnoop?  It would explain.


Takashi

  reply	other threads:[~2024-04-01 11:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-31 20:21 regression/bisected/6.9 commit 587d67fd929ad89801bcc429675bda90d53f6592 decrease 30% of gaming performance Mikhail Gavrilov
2024-04-01  7:07 ` Takashi Iwai
2024-04-01 11:07   ` Mikhail Gavrilov
2024-04-01 11:41     ` Takashi Iwai [this message]
2024-04-01 13:49       ` Mikhail Gavrilov
2024-04-01 14:48         ` Takashi Iwai
2024-04-01 16:50           ` Mikhail Gavrilov
2024-04-01 19:29             ` mikhail.v.gavrilov
2024-04-18  6:22               ` Mikhail Gavrilov
2024-04-24 13:21                 ` Mikhail Gavrilov
2024-04-24 13:33                   ` Takashi Iwai
2024-04-24 13:42                     ` Takashi Iwai
2024-04-29 23:00                       ` Mikhail Gavrilov
2024-04-30  5:51                         ` Takashi Iwai
2024-04-30 10:54                           ` Mikhail Gavrilov
2024-04-30 12:12                             ` Takashi Iwai
2024-04-30 14:42                               ` Mikhail Gavrilov

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=87v851e2di.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mikhail.v.gavrilov@gmail.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