From: Takashi Iwai <tiwai@suse.de>
To: Sven van Ashbrook <svenva@chromium.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Hillf Danton <hdanton@sina.com>,
Karthikeyan Ramasubramanian <kramasub@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Brian Geffon <bgeffon@google.com>,
linux-sound@vger.kernel.org, "Arava,
Jairaj" <jairaj.arava@intel.com>,
Curtis Malainey <cujomalainey@chromium.org>
Subject: Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case
Date: Mon, 19 Feb 2024 12:19:55 +0100 [thread overview]
Message-ID: <87le7gog4k.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAG-rBihE31G1q0pXbdR22bHKNboiADTUHx0JMnDKBg_sua+0RA@mail.gmail.com>
On Fri, 16 Feb 2024 17:22:45 +0100,
Sven van Ashbrook wrote:
>
> On Fri, Feb 16, 2024 at 9:43 AM Takashi Iwai <tiwai@suse.de> wrote:
> >
> > OK, then how about the one like below?
> >
> > This changes:
> > - Back to __GFP_NORETRY as default
> > - Use __GFP_RETRY_MAYFAIL for SNDRV_DMA_TYPE_NONCONTIG with IOMMU;
> > this should cover the commit a61c7d88d38c
> > - Also use __GFP_RETRY_MAYFAIL for the SG-fallback allocations of the
> > minimal order, just like IOMMU allocator does.
> >
> > This should be less destructive, while still allowing more aggressive
> > allocations for SG buffers.
>
> This one looks like it would keep the SOF firmware allocation issue at bay,
> in both iommu and non-iommu cases.
>
> If there is no further discussion in this thread, we'll stress test this
> on iommu and non-iommu Chromebooks.
The test with my latest patch would be appreciated in anyway.
thanks,
Takashi
next prev parent reply other threads:[~2024-02-19 11:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 0:07 [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case Karthikeyan Ramasubramanian
2024-02-15 3:45 ` Hillf Danton
2024-02-15 8:40 ` Takashi Iwai
2024-02-15 16:07 ` Sven van Ashbrook
2024-02-15 17:03 ` Takashi Iwai
2024-02-15 19:32 ` Karthikeyan Ramasubramanian
2024-02-16 7:47 ` Takashi Iwai
2024-02-16 4:34 ` Hillf Danton
2024-02-16 8:35 ` Takashi Iwai
2024-02-16 10:18 ` Takashi Iwai
2024-02-16 12:19 ` Kai Vehmanen
2024-02-16 14:43 ` Takashi Iwai
2024-02-16 16:22 ` Sven van Ashbrook
2024-02-19 11:19 ` Takashi Iwai [this message]
2024-02-21 18:09 ` Karthikeyan Ramasubramanian
2024-02-16 10:51 ` Hillf Danton
2024-02-19 11:36 ` Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case) Takashi Iwai
2024-02-19 11:40 ` Vlastimil Babka
2024-02-20 15:52 ` Sven van Ashbrook
2024-02-21 9:21 ` Takashi Iwai
2024-02-21 15:37 ` Sven van Ashbrook
2024-02-21 9:58 ` Vlastimil Babka
2024-02-21 15:40 ` Sven van Ashbrook
2024-02-21 11:43 ` [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations Vlastimil Babka
2024-02-21 15:52 ` Sven van Ashbrook
2024-02-22 16:43 ` Karthikeyan Ramasubramanian
2024-02-26 16:09 ` Sven van Ashbrook
2024-02-26 16:45 ` Vlastimil Babka
2024-02-28 19:33 ` Karthikeyan Ramasubramanian
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=87le7gog4k.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=bgeffon@google.com \
--cc=cujomalainey@chromium.org \
--cc=hdanton@sina.com \
--cc=jairaj.arava@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kramasub@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=svenva@chromium.org \
/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