From: ebiederm@xmission.com (Eric W. Biederman)
To: Colin Cross <ccross@android.com>
Cc: linux-kernel@vger.kernel.org,
Kyungmin Park <kmpark@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
John Stultz <john.stultz@linaro.org>,
Rob Landley <rob@landley.net>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Cyrill Gorcunov <gorcunov@openvz.org>,
David Rientjes <rientjes@google.com>,
Davidlohr Bueso <dave@gnu.org>, Kees Cook <keescook@chromium.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Michel Lespinasse <walken@google.com>,
Rik van Riel <riel@redhat.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rusty Russell <rusty@rustcorp.com.au>,
Oleg Nesterov <oleg@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
KAMEZ AWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Michal Hocko <mhocko@suse.cz>Anton Vorontsov <a>
Subject: Re: [PATCH] mm: add sys_madvise2 and MADV_NAME to name vmas
Date: Wed, 03 Jul 2013 21:54:55 -0700 [thread overview]
Message-ID: <87txkaq600.fsf@xmission.com> (raw)
In-Reply-To: <1372901537-31033-1-git-send-email-ccross@android.com> (Colin Cross's message of "Wed, 3 Jul 2013 18:31:56 -0700")
Colin Cross <ccross@android.com> writes:
> Userspace processes often have multiple allocators that each do
> anonymous mmaps to get memory. When examining memory usage of
> individual processes or systems as a whole, it is useful to be
> able to break down the various heaps that were allocated by
> each layer and examine their size, RSS, and physical memory
> usage.
What is the advantage of this? It looks like it is going to add cache
line contention (atomic_inc/atomic_dec) to every vma operation
especially in the envision use case of heavy vma_name sharing.
I would expect this will result in a bloated vm_area_struct and a slower
mm subsystem.
Have you done any benchmarks that stress the mm subsystem?
How can adding glittler to /proc/<pid>/maps and /proc/<pid>/smaps
justify putting a hand break on the linux kernel?
Eric
> +/**
> + * vma_name_get
> + *
> + * Increment the refcount of an existing vma_name. No locks are needed because
> + * the caller should already be holding a reference, so refcount >= 1.
> + */
> +void vma_name_get(struct vma_name *vma_name)
> +{
> + if (WARN_ON(!vma_name))
> + return;
> +
> + WARN_ON(!atomic_read(&vma_name->refcount));
> +
> + atomic_inc(&vma_name->refcount);
> +}
> +
> +/**
> + * vma_name_put
> + *
> + * Decrement the refcount of an existing vma_name and free it if necessary.
> + * No locks needed, takes the cache lock if it needs to remove the vma_name from
> + * the cache.
> + */
> +void vma_name_put(struct vma_name *vma_name)
> +{
> + int ret;
> +
> + if (WARN_ON(!vma_name))
> + return;
> +
> + WARN_ON(!atomic_read(&vma_name->refcount));
> +
> + /* fast path: refcount > 1, decrement and return */
> + if (atomic_add_unless(&vma_name->refcount, -1, 1))
> + return;
> +
> + /* slow path: take the lock, decrement, and erase node if count is 0 */
> + write_lock(&vma_name_cache_lock);
> +
> + ret = atomic_dec_return(&vma_name->refcount);
> + if (ret == 0)
> + rb_erase(&vma_name->rb_node, &vma_name_cache);
> +
> + write_unlock(&vma_name_cache_lock);
> +
> + if (ret == 0)
> + kfree(vma_name);
> +}
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Colin Cross <ccross@android.com>
Cc: linux-kernel@vger.kernel.org,
Kyungmin Park <kmpark@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
John Stultz <john.stultz@linaro.org>,
Rob Landley <rob@landley.net>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Cyrill Gorcunov <gorcunov@openvz.org>,
David Rientjes <rientjes@google.com>,
Davidlohr Bueso <dave@gnu.org>, Kees Cook <keescook@chromium.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Michel Lespinasse <walken@google.com>,
Rik van Riel <riel@redhat.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rusty Russell <rusty@rustcorp.com.au>,
Oleg Nesterov <oleg@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Michal Hocko <mhocko@suse.cz>,
Anton Vorontsov <anton.vorontsov@linaro.org>,
Pekka Enberg <penberg@kernel.org>, Shaohua Li <shli@fusionio.com>,
Sasha Levin <sasha.levin@oracle.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Ingo Molnar <mingo@kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
"open list:GENERIC INCLUDE/A..." <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] mm: add sys_madvise2 and MADV_NAME to name vmas
Date: Wed, 03 Jul 2013 21:54:55 -0700 [thread overview]
Message-ID: <87txkaq600.fsf@xmission.com> (raw)
In-Reply-To: <1372901537-31033-1-git-send-email-ccross@android.com> (Colin Cross's message of "Wed, 3 Jul 2013 18:31:56 -0700")
Colin Cross <ccross@android.com> writes:
> Userspace processes often have multiple allocators that each do
> anonymous mmaps to get memory. When examining memory usage of
> individual processes or systems as a whole, it is useful to be
> able to break down the various heaps that were allocated by
> each layer and examine their size, RSS, and physical memory
> usage.
What is the advantage of this? It looks like it is going to add cache
line contention (atomic_inc/atomic_dec) to every vma operation
especially in the envision use case of heavy vma_name sharing.
I would expect this will result in a bloated vm_area_struct and a slower
mm subsystem.
Have you done any benchmarks that stress the mm subsystem?
How can adding glittler to /proc/<pid>/maps and /proc/<pid>/smaps
justify putting a hand break on the linux kernel?
Eric
> +/**
> + * vma_name_get
> + *
> + * Increment the refcount of an existing vma_name. No locks are needed because
> + * the caller should already be holding a reference, so refcount >= 1.
> + */
> +void vma_name_get(struct vma_name *vma_name)
> +{
> + if (WARN_ON(!vma_name))
> + return;
> +
> + WARN_ON(!atomic_read(&vma_name->refcount));
> +
> + atomic_inc(&vma_name->refcount);
> +}
> +
> +/**
> + * vma_name_put
> + *
> + * Decrement the refcount of an existing vma_name and free it if necessary.
> + * No locks needed, takes the cache lock if it needs to remove the vma_name from
> + * the cache.
> + */
> +void vma_name_put(struct vma_name *vma_name)
> +{
> + int ret;
> +
> + if (WARN_ON(!vma_name))
> + return;
> +
> + WARN_ON(!atomic_read(&vma_name->refcount));
> +
> + /* fast path: refcount > 1, decrement and return */
> + if (atomic_add_unless(&vma_name->refcount, -1, 1))
> + return;
> +
> + /* slow path: take the lock, decrement, and erase node if count is 0 */
> + write_lock(&vma_name_cache_lock);
> +
> + ret = atomic_dec_return(&vma_name->refcount);
> + if (ret == 0)
> + rb_erase(&vma_name->rb_node, &vma_name_cache);
> +
> + write_unlock(&vma_name_cache_lock);
> +
> + if (ret == 0)
> + kfree(vma_name);
> +}
--
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>
next prev parent reply other threads:[~2013-07-04 4:54 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 1:31 [PATCH] mm: add sys_madvise2 and MADV_NAME to name vmas Colin Cross
2013-07-04 1:31 ` Colin Cross
2013-07-04 4:54 ` Eric W. Biederman [this message]
2013-07-04 4:54 ` Eric W. Biederman
2013-07-04 6:32 ` Colin Cross
2013-07-04 6:32 ` Colin Cross
2013-07-05 16:52 ` Oleg Nesterov
2013-07-05 16:52 ` Oleg Nesterov
2013-07-06 6:33 ` Pekka Enberg
2013-07-06 6:33 ` Pekka Enberg
2013-07-06 11:53 ` Eric W. Biederman
2013-07-06 11:53 ` Eric W. Biederman
2013-07-07 18:35 ` Colin Cross
2013-07-07 18:35 ` Colin Cross
2013-07-14 1:38 ` Simon Jeons
2013-07-04 8:56 ` Peter Zijlstra
2013-07-04 8:56 ` Peter Zijlstra
2013-07-05 20:25 ` Colin Cross
2013-07-05 20:25 ` Colin Cross
2013-07-10 23:20 ` Dave Hansen
2013-07-10 23:20 ` Dave Hansen
2013-07-04 20:22 ` Oleg Nesterov
2013-07-04 20:22 ` Oleg Nesterov
2013-07-05 19:40 ` Colin Cross
2013-07-05 19:40 ` Colin Cross
2013-07-08 18:04 ` [PATCH 0/1] mm: mempolicy: (Was: add sys_madvise2 and MADV_NAME to name vmas) Oleg Nesterov
2013-07-08 18:04 ` Oleg Nesterov
2013-07-08 18:05 ` [PATCH 1/1] mm: mempolicy: fix mbind_range() && vma_adjust() interaction Oleg Nesterov
2013-07-08 18:05 ` Oleg Nesterov
2013-07-08 22:29 ` KOSAKI Motohiro
2013-07-08 22:29 ` KOSAKI Motohiro
2013-07-09 15:28 ` Oleg Nesterov
2013-07-09 15:28 ` Oleg Nesterov
2013-07-09 19:43 ` Oleg Nesterov
2013-07-09 19:43 ` Oleg Nesterov
2013-07-10 2:49 ` KOSAKI Motohiro
2013-07-10 2:49 ` KOSAKI Motohiro
2013-07-09 21:56 ` Andrew Morton
2013-07-09 21:56 ` Andrew Morton
2013-07-10 15:45 ` Oleg Nesterov
2013-07-10 15:45 ` Oleg Nesterov
2013-07-24 9:40 ` [PATCH] mm: add sys_madvise2 and MADV_NAME to name vmas Jan Glauber
2013-07-24 9:40 ` Jan Glauber
2013-07-24 20:05 ` Colin Cross
2013-07-24 20:05 ` Colin Cross
2013-07-10 23:08 ` Dave Hansen
2013-07-10 23:08 ` Dave Hansen
[not found] ` <CAMbhsRTio2mS=azWTxSdRdaZJRRf5FfMNoQUZmrFjkB7kv9LSQ@mail.gmail.com>
2013-07-10 23:38 ` Dave Hansen
2013-07-10 23:38 ` Dave Hansen
[not found] ` <CAMbhsRTs45QE1ze6mvdiL2QYKD0dHjXoRk7o1h2Y_rYP80ckDg@mail.gmail.com>
2013-07-11 0:19 ` Dave Hansen
2013-07-11 0:19 ` Dave Hansen
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=87txkaq600.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ccross@android.com \
--cc=dave@gnu.org \
--cc=gorcunov@openvz.org \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=john.stultz@linaro.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=keescook@chromium.org \
--cc=khlebnikov@openvz.org \
--cc=kmpark@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=oleg@redhat.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=srikar@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@google.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.