Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Das, Nirmoy" <nirmoy.das@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Cc: matthew.auld@intel.com, chris.p.wilson@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Suppress oom warning for shmemfs object allocation failure
Date: Tue, 26 Jul 2022 16:49:51 +0200	[thread overview]
Message-ID: <5166fd90-7f37-0198-4222-cb7a7286753c@intel.com> (raw)
In-Reply-To: <20220726144714.18251-1-nirmoy.das@intel.com>

Please ignore this one.


Nirmoy

On 7/26/2022 4:47 PM, Nirmoy Das wrote:
> From: Chris Wilson <chris@chris-wilson.co.uk>
>
> We report object allocation failures to userspace with ENOMEM, yet we
> still show the memory warning after failing to shrink device allocated
> pages. While this warning is similar to other system page allocation
> failures, it is superfluous to the ENOMEM provided directly to
> userspace.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4936
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
>   drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> index 4eed3dd90ba8..4466173e1bcc 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> @@ -137,7 +137,7 @@ int shmem_sg_alloc_table(struct drm_i915_private *i915, struct sg_table *st,
>   				 * trigger the out-of-memory killer and for
>   				 * this we want __GFP_RETRY_MAYFAIL.
>   				 */
> -				gfp |= __GFP_RETRY_MAYFAIL;
> +				gfp |= __GFP_RETRY_MAYFAIL | __GFP_NOWARN;
>   			}
>   		} while (1);
>   

  reply	other threads:[~2022-07-26 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 14:47 [Intel-gfx] [PATCH] drm/i915: Suppress oom warning for shmemfs object allocation failure Nirmoy Das
2022-07-26 14:49 ` Das, Nirmoy [this message]
2022-07-26 15:01 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Suppress oom warning for shmemfs object allocation failure (rev3) Patchwork
2022-07-26 15:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-26 17:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2022-07-27 17:40 [Intel-gfx] [PATCH] drm/i915: Suppress oom warning for shmemfs object allocation failure Nirmoy Das
2022-07-27 20:36 ` Andi Shyti
2022-07-20 12:23 Nirmoy Das
2022-07-20 12:39 ` Andrzej Hajda
2022-07-21  9:49 ` Matthew Auld
2022-07-21 12:21   ` Das, Nirmoy

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=5166fd90-7f37-0198-4222-cb7a7286753c@intel.com \
    --to=nirmoy.das@intel.com \
    --cc=chris.p.wilson@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.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