From: Hugh Dickins <hughd@google.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: akpm@linux-foundation.org, mingo@kernel.org,
peterz@infradead.org, riel@redhat.com, mgorman@suse.de,
aswin@hp.com, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] mm/rmap: share the i_mmap_rwsem
Date: Mon, 26 May 2014 12:35:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.1405261216460.3411@eggly.anvils> (raw)
In-Reply-To: <1400816006-3083-5-git-send-email-davidlohr@hp.com>
On Thu, 22 May 2014, Davidlohr Bueso wrote:
> Similarly to rmap_walk_anon() and collect_procs_anon(),
> there is opportunity to share the lock in rmap_walk_file()
> and collect_procs_file() for file backed pages.
And lots of other places, no? I welcome i_mmap_rwsem, but I think
you're approaching it wrongly to separate this off from 2/5, then
follow anon_vma for the places that can be converted to lock_read().
If you go back through 2/5 and study the context of each, I think
you'll find most make no modification to the tree, and can well
use the lock_read() rather than the lock_write().
I could be wrong, but I don't think there are any hidden gotchas.
There certainly are in the anon_vma case (where THP makes special
use of the anon_vma lock), and used to be in the i_mmap_lock case
(when invalidation had to be single-threaded across cond_rescheds),
but I think i_mmap_rwsem should be straightforward.
Sure, it's safe to use the lock_write() variant, but please don't
prefer it to lock_read() without good reason.
Hugh
>
> Signed-off-by: Davidlohr Bueso <davidlohr@hp.com>
> ---
> include/linux/fs.h | 10 ++++++++++
> mm/memory-failure.c | 4 ++--
> mm/rmap.c | 4 ++--
> 3 files changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 60a1d7d..4c2c228 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -467,6 +467,16 @@ static inline void i_mmap_unlock_write(struct address_space *mapping)
> up_write(&mapping->i_mmap_rwsem);
> }
>
> +static inline void i_mmap_lock_read(struct address_space *mapping)
> +{
> + down_read(&mapping->i_mmap_rwsem);
> +}
> +
> +static inline void i_mmap_unlock_read(struct address_space *mapping)
> +{
> + up_read(&mapping->i_mmap_rwsem);
> +}
> +
> /*
> * Might pages of this file be mapped into userspace?
> */
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index 1389a28..acbcd8e 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -434,7 +434,7 @@ static void collect_procs_file(struct page *page, struct list_head *to_kill,
> struct task_struct *tsk;
> struct address_space *mapping = page->mapping;
>
> - i_mmap_lock_write(mapping);
> + i_mmap_lock_read(mapping);
> read_lock(&tasklist_lock);
> for_each_process(tsk) {
> pgoff_t pgoff = page_pgoff(page);
> @@ -456,7 +456,7 @@ static void collect_procs_file(struct page *page, struct list_head *to_kill,
> }
> }
> read_unlock(&tasklist_lock);
> - i_mmap_unlock_write(mapping);
> + i_mmap_unlock_read(mapping);
> }
>
> /*
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 9a56e4f..5841dcb 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1685,7 +1685,7 @@ static int rmap_walk_file(struct page *page, struct rmap_walk_control *rwc)
>
> if (!mapping)
> return ret;
> - i_mmap_lock_write(mapping);
> + i_mmap_lock_read(mapping);
> vma_interval_tree_foreach(vma, &mapping->i_mmap, pgoff, pgoff) {
> unsigned long address = vma_address(page, vma);
>
> @@ -1708,7 +1708,7 @@ static int rmap_walk_file(struct page *page, struct rmap_walk_control *rwc)
> ret = rwc->file_nonlinear(page, mapping, rwc->arg);
>
> done:
> - i_mmap_unlock_write(mapping);
> + i_mmap_unlock_read(mapping);
> return ret;
> }
>
> --
> 1.8.1.4
--
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:[~2014-05-26 19:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 3:33 [PATCH 0/5] mm: i_mmap_mutex to rwsem Davidlohr Bueso
2014-05-23 3:33 ` [PATCH 1/5] mm,fs: introduce helpers around i_mmap_mutex Davidlohr Bueso
2014-05-23 17:16 ` Rik van Riel
2014-05-23 3:33 ` [PATCH 2/5] mm: use new helper functions around the i_mmap_mutex Davidlohr Bueso
2014-05-23 17:16 ` Rik van Riel
2014-05-23 3:33 ` [PATCH 3/5] mm: convert i_mmap_mutex to rwsem Davidlohr Bueso
2014-05-23 17:33 ` Rik van Riel
2014-05-23 3:33 ` [PATCH 4/5] mm/rmap: share the i_mmap_rwsem Davidlohr Bueso
2014-05-23 18:35 ` Rik van Riel
2014-05-26 19:35 ` Hugh Dickins [this message]
2014-05-26 20:48 ` Davidlohr Bueso
2014-05-23 3:33 ` [PATCH 5/5] mm: rename leftover i_mmap_mutex Davidlohr Bueso
2014-05-23 18:36 ` Rik van Riel
2014-05-30 2:20 ` [PATCH 0/5] mm: i_mmap_mutex to rwsem Davidlohr Bueso
2014-06-02 20:08 ` Andrew Morton
2014-06-02 20:31 ` Davidlohr Bueso
2014-06-02 23:54 ` Hugh Dickins
-- strict thread matches above, loose matches on Subject: below --
2013-06-25 0:21 Davidlohr Bueso
2013-06-25 0:21 ` [PATCH 4/5] mm/rmap: share the i_mmap_rwsem Davidlohr Bueso
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=alpine.LSU.2.11.1405261216460.3411@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox