From: Minchan Kim <minchan@kernel.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [RFC 3/4] mm: support remove_mapping in irqcontext
Date: Tue, 14 May 2013 16:17:18 +0900 [thread overview]
Message-ID: <20130514071718.GC9466@blaptop> (raw)
In-Reply-To: <20130513145857.GD5246@dhcp22.suse.cz>
Hey Michal,
On Mon, May 13, 2013 at 04:58:57PM +0200, Michal Hocko wrote:
> On Mon 13-05-13 11:10:47, Minchan Kim wrote:
> [...]
> > My rough plan is following as,
> >
> > 1. Make mctz->lock beging aware of irq by changing spin_lock with
> > spin_lock_irqsave.
>
> I wouldn't be worried about this one as it is on its way out with the
> soft limit rework (the core uncontroversial part ;))
Good to hear!
>
> > 2. Introuduce new argument "locked" in __mem_cgroup_uncharge_common
> > so that __mem_cgroup_uncharge_common can avoid lock_page_cgroup in
> > irqcontext to avoid deadlock but caller in irqcontext should be held
> > it in advance by next patch.
> > 3. Introduce try_lock_page_cgroup, which will be used __swapcache_free.
> > 4. __remove_mapping can held a page_cgroup lock in advance before calling
> > __swapcache_free
> >
> > I'd like to listen memcg people's opinions before diving into coding.
>
> It should work. It will require some code moving, though.
Yeb. I will give it a shot!
Thanks for the review!
--
Kind regards,
Minchan Kim
--
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: Minchan Kim <minchan@kernel.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [RFC 3/4] mm: support remove_mapping in irqcontext
Date: Tue, 14 May 2013 16:17:18 +0900 [thread overview]
Message-ID: <20130514071718.GC9466@blaptop> (raw)
In-Reply-To: <20130513145857.GD5246@dhcp22.suse.cz>
Hey Michal,
On Mon, May 13, 2013 at 04:58:57PM +0200, Michal Hocko wrote:
> On Mon 13-05-13 11:10:47, Minchan Kim wrote:
> [...]
> > My rough plan is following as,
> >
> > 1. Make mctz->lock beging aware of irq by changing spin_lock with
> > spin_lock_irqsave.
>
> I wouldn't be worried about this one as it is on its way out with the
> soft limit rework (the core uncontroversial part ;))
Good to hear!
>
> > 2. Introuduce new argument "locked" in __mem_cgroup_uncharge_common
> > so that __mem_cgroup_uncharge_common can avoid lock_page_cgroup in
> > irqcontext to avoid deadlock but caller in irqcontext should be held
> > it in advance by next patch.
> > 3. Introduce try_lock_page_cgroup, which will be used __swapcache_free.
> > 4. __remove_mapping can held a page_cgroup lock in advance before calling
> > __swapcache_free
> >
> > I'd like to listen memcg people's opinions before diving into coding.
>
> It should work. It will require some code moving, though.
Yeb. I will give it a shot!
Thanks for the review!
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2013-05-14 7:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 2:10 [RFC 0/4] free reclaimed pages by paging out instantly Minchan Kim
2013-05-13 2:10 ` Minchan Kim
2013-05-13 2:10 ` [RFC 1/4] mm: Don't hide spin_lock in swap_info_get Minchan Kim
2013-05-13 2:10 ` Minchan Kim
2013-05-13 2:10 ` [RFC 2/4] mm: introduce __swapcache_free Minchan Kim
2013-05-13 2:10 ` Minchan Kim
2013-05-13 2:10 ` [RFC 3/4] mm: support remove_mapping in irqcontext Minchan Kim
2013-05-13 2:10 ` Minchan Kim
2013-05-13 14:58 ` Michal Hocko
2013-05-13 14:58 ` Michal Hocko
2013-05-14 7:17 ` Minchan Kim [this message]
2013-05-14 7:17 ` Minchan Kim
2013-05-13 2:10 ` [RFC 4/4] mm: free reclaimed pages instantly without depending next reclaim Minchan Kim
2013-05-13 2:10 ` Minchan Kim
2013-05-14 17:32 ` Rik van Riel
2013-05-14 17:32 ` Rik van Riel
2013-05-15 7:12 ` Minchan Kim
2013-05-15 7:12 ` Minchan Kim
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=20130514071718.GC9466@blaptop \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=riel@redhat.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.