From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f71.google.com (mail-wm0-f71.google.com [74.125.82.71]) by kanga.kvack.org (Postfix) with ESMTP id 7476B831F4 for ; Mon, 22 May 2017 05:37:29 -0400 (EDT) Received: by mail-wm0-f71.google.com with SMTP id g143so24647128wme.13 for ; Mon, 22 May 2017 02:37:29 -0700 (PDT) Received: from mx1.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id k12si32456493wmi.110.2017.05.22.02.37.27 for (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 22 May 2017 02:37:27 -0700 (PDT) Date: Mon, 22 May 2017 11:37:25 +0200 From: Michal Hocko Subject: Re: [PATCH] dm ioctl: Restore __GFP_HIGH in copy_params() Message-ID: <20170522093725.GF8509@dhcp22.suse.cz> References: <20170518185040.108293-1-junaids@google.com> <20170518190406.GB2330@dhcp22.suse.cz> <1508444.i5EqlA1upv@js-desktop.svl.corp.google.com> <20170519074647.GC13041@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Mikulas Patocka Cc: Junaid Shahid , David Rientjes , Alasdair Kergon , Mike Snitzer , Andrew Morton , linux-mm@kvack.org, andreslc@google.com, gthelen@google.com, vbabka@suse.cz, linux-kernel@vger.kernel.org On Fri 19-05-17 19:43:23, Mikulas Patocka wrote: > > > On Fri, 19 May 2017, Michal Hocko wrote: > > > On Thu 18-05-17 19:50:46, Junaid Shahid wrote: > > > (Adding back the correct linux-mm email address and also adding linux-kernel.) > > > > > > On Thursday, May 18, 2017 01:41:33 PM David Rientjes wrote: > > [...] > > > > Let's ask Mikulas, who changed this from PF_MEMALLOC to __GFP_HIGH, > > > > assuming there was a reason to do it in the first place in two different > > > > ways. > > > > Hmm, the old PF_MEMALLOC used to have the following comment > > /* > > * Trying to avoid low memory issues when a device is > > * suspended. > > */ > > > > I am not really sure what that means but __GFP_HIGH certainly have a > > different semantic than PF_MEMALLOC. The later grants the full access to > > the memory reserves while the prior on partial access. If this is _really_ > > needed then it deserves a comment explaining why. > > -- > > Michal Hocko > > SUSE Labs > > Sometimes, I/O to a device mapper device is blocked until the userspace > daemon dmeventd does some action (for example, when dm-mirror leg fails, > dmeventd needs to mark the leg as failed in the lvm metadata and then > reload the device). > > The dmeventd daemon mlocks itself in memory so that it doesn't generate > any I/O. But it must be able to call ioctls. __GFP_HIGH is there so that > the ioctls issued by dmeventd have higher chance of succeeding if some I/O > is blocked, waiting for dmeventd action. It reduces the possibility of > low-memory-deadlock, though it doesn't eliminate it entirely. So what happens if the memory reserves are depleted. Do we deadlock? Why is OOM killer insufficient to allow the further progress? -- Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org