From: Takashi Iwai <tiwai@suse.de>
To: Hillf Danton <hdanton@sina.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Sven van Ashbrook <svenva@chromium.org>,
Karthikeyan Ramasubramanian <kramasub@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Brian Geffon <bgeffon@google.com>,
linux-sound@vger.kernel.org,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case
Date: Fri, 16 Feb 2024 09:35:32 +0100 [thread overview]
Message-ID: <87plwwiz6z.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240216043426.1218-1-hdanton@sina.com>
On Fri, 16 Feb 2024 05:34:24 +0100,
Hillf Danton wrote:
>
> On Thu, 15 Feb 2024 18:03:01 +0100 Takashi Iwai <tiwai@suse.de> wrote:
> >
> > So it sounds like that we should go back for __GFP_NORETRY in general
> > for non-zero order allocations, not only the call you changed, as
> > __GFP_RETRY_MAYFAIL doesn't guarantee the stuck.
> >
> > How about the changes like below?
> >
> > +/* default GFP bits for our allocations */
> > +static gfp_t default_gfp(size_t size)
> > +{
> > + /* don't allocate intensively for high-order pages */
> > + if (size > PAGE_SIZE)
> > + return GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY;
> > + else
> > + return GFP_KERNEL | __GFP_NOWARN | __GFP_RETRY_MAYFAIL;
> > +}
>
> Looks like an overdose because both __GFP_NORETRY and __GFP_RETRY_MAYFAIL
> are checked in __alloc_pages_slowpath().
If the check there worked as expected, this shouldn't have been a
problem, no?
The fact that we have to drop __GFP_RETRY_MAYFAIL indicates that the
handling there doesn't suffice -- at least for the audio operation.
thanks,
Takashi
next prev parent reply other threads:[~2024-02-16 8:35 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 [this message]
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
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=87plwwiz6z.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=bgeffon@google.com \
--cc=hdanton@sina.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 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.