With this patch, the test results have been promising so far. After 10 hours of stress testing, we have not hit the reported problem yet. We will keep testing and report here if we hit the problem again. Thanks for engaging with us. On Wed, Feb 21, 2024 at 8:53 AM Sven van Ashbrook <svenva@xxxxxxxxxxxx> wrote: > > Thanks so much ! We will stress test this on our side. > > We do this by exhausting memory and triggering many suspend/resume > cycles. This reliably reproduces the problem (before this patch). > > Of course, as we all know, absence of evidence (no more stalls in stress tests) > does not equal evidence of absence (stalls are gone in all code paths).
- References:
- Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- From: Sven van Ashbrook
- [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
- From: Vlastimil Babka
- Re: [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
- From: Sven van Ashbrook
- Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- Prev by Date: [PATCH usb next] ASoC: Revert "ASoC: dt-bindings: Update example for enabling USB offload on SM8250"
- Next by Date: Re: [PATCH v17 36/51] ASoC: dt-bindings: Update example for enabling USB offload on SM8250
- Previous by thread: Re: [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
- Next by thread: Re: [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
- Index(es):