All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@parallels.com>
To: Anton Vorontsov <anton@enomsg.org>
Cc: Glauber Costa <glommer@openvz.org>,
	linux-mm@kvack.org, cgroups@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Dave Chinner <david@fromorbit.com>,
	John Stultz <john.stultz@linaro.org>,
	Joonsoo Kim <js1304@gmail.com>, Michal Hocko <mhocko@suse.cz>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH 1/2] vmpressure: in-kernel notifications
Date: Tue, 23 Apr 2013 11:17:08 -0700	[thread overview]
Message-ID: <5176D024.5090007@parallels.com> (raw)
In-Reply-To: <20130423171122.GA29983@teo>

On 04/23/2013 10:11 AM, Anton Vorontsov wrote:
> On Tue, Apr 23, 2013 at 12:22:08PM +0400, Glauber Costa wrote:
>> From: Glauber Costa <glommer@parallels.com>
> [...]
>> This patch extends that to also support in-kernel users.
>
> Yup, that is the next logical step. ;-) The patches look good to me, just
> one question...
>
>> @@ -227,7 +233,7 @@ void vmpressure(gfp_t gfp, struct mem_cgroup *memcg,
>>   	 * we account it too.
>>   	 */
>>   	if (!(gfp & (__GFP_HIGHMEM | __GFP_MOVABLE | __GFP_IO | __GFP_FS)))
>
> I wonder if we want to let kernel users to specify the gfp mask here? The
> current mask is good for userspace notifications, but in-kernel users
> might be interested in including (or excluding) different types of
> allocations, e.g. watch only for DMA allocations pressure?
>

That is outside of the scope of this patch anyway. For this one, if you 
believe it is good, could I have your tag? =)

But answering your question regardless of the scope, I believe the 
context of the allocation is an implementation detail of the kernel - 
regardless of how widely understood it is. The thing I like the most 
about your work, is precisely the fact that is hides the implementation 
details so well.

So unless there is a strong use case that would benefit from it, I am 
inclined to say this is not wanted.

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2013-04-23 18:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23  8:22 [PATCH 0/2] reuse vmpressure for in-kernel events Glauber Costa
2013-04-23  8:22 ` Glauber Costa
     [not found] ` <1366705329-9426-1-git-send-email-glommer-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2013-04-23  8:22   ` [PATCH 1/2] vmpressure: in-kernel notifications Glauber Costa
2013-04-23  8:22     ` Glauber Costa
     [not found]     ` <1366705329-9426-2-git-send-email-glommer-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2013-04-23 17:11       ` Anton Vorontsov
2013-04-23 17:11         ` Anton Vorontsov
2013-04-23 18:17         ` Glauber Costa [this message]
2013-04-23 19:13       ` Pekka Enberg
2013-04-23 19:13         ` Pekka Enberg
2013-04-24 19:42       ` Greg Thelen
2013-04-24 19:42         ` Greg Thelen
2013-04-24 20:04         ` Glauber Costa
2013-04-25 10:50         ` Glauber Costa
2013-04-25 18:34           ` Greg Thelen
2013-04-23 20:24     ` Anton Vorontsov
2013-04-23 21:01       ` Anton Vorontsov
2013-04-23 21:01         ` Anton Vorontsov
2013-04-24  6:26       ` Glauber Costa
2013-04-24 11:20       ` Glauber Costa
2013-04-24  7:21     ` Greg Thelen
2013-04-24  8:36       ` Glauber Costa
2013-04-24 19:35         ` Greg Thelen
2013-04-23  8:22   ` [PATCH 2/2] memcg: reap dead memcgs under pressure Glauber Costa
2013-04-23  8:22     ` Glauber Costa
2013-04-25 12:50     ` Li Zefan
2013-04-26  7:38       ` Glauber Costa

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=5176D024.5090007@parallels.com \
    --to=glommer@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@enomsg.org \
    --cc=cgroups@vger.kernel.org \
    --cc=david@fromorbit.com \
    --cc=glommer@openvz.org \
    --cc=hannes@cmpxchg.org \
    --cc=john.stultz@linaro.org \
    --cc=js1304@gmail.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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.