All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
	Nirmoy Das <nirmoy.das@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/gem: Suppress oom warning in favour of ENOMEM to userspace
Date: Thu, 27 Jun 2024 18:56:53 +0200	[thread overview]
Message-ID: <fe18bed7-5a25-4abb-9745-e887d8211de8@linux.intel.com> (raw)
In-Reply-To: <Zn05EPD0PRLdUmuj@ashyti-mobl2.lan>

Hi Andi,

On 6/27/2024 12:04 PM, Andi Shyti wrote:
> Hi Nirmoy,
>
> On Wed, Jun 26, 2024 at 04:33:18PM +0200, Nirmoy Das wrote:
>> We report object allocation failures to userspace with ENOMEM
>> so add __GFP_NOWARN to remove superfluous oom warnings.
> I think this should be the default behavior.
Yes, when drivers handle ENOMEM situation which is the case for i915/gem 
code
>   ENOMEM doesn't
> necessarily mean that there is a kernel failure. Most of the time
> we just run out of memory, deal with it :-)
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>

Thanks!


>
> Thanks,
> Andi

  reply	other threads:[~2024-06-27 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 14:33 [PATCH] drm/i915/gem: Suppress oom warning in favour of ENOMEM to userspace Nirmoy Das
2024-06-26 15:24 ` Rodrigo Vivi
2024-06-26 15:36   ` Nirmoy Das
2024-06-26 15:50     ` Rodrigo Vivi
2024-06-26 21:07       ` Nirmoy Das
2024-06-26 17:02 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-06-27  2:09 ` ✓ Fi.CI.IGT: " Patchwork
2024-06-27 10:04 ` [PATCH] " Andi Shyti
2024-06-27 16:56   ` Nirmoy Das [this message]
2024-06-27 22:36     ` Andi Shyti

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=fe18bed7-5a25-4abb-9745-e887d8211de8@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nirmoy.das@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 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.