From: Paul Jackson <pj@sgi.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: ak@suse.de, akpm@osdl.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: Does shmem_getpage==>shmem_alloc_page==>alloc_page_vma hold mmap_sem?
Date: Sat, 5 Nov 2005 22:17:28 -0800 [thread overview]
Message-ID: <20051105221728.3fa25f69.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0511060547120.14675@goblin.wat.veritas.com>
Hugh wrote:
> It's safe but horrid.
Ok - thanks for the explanation.
Now I don't feel so bad about some of my cpuset locking hacks.
(Yes, Andrew, I'm still looking at my latest hack,
the down_write_trylock() call in cpuset.c refresh_mems.)
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
--
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>
prev parent reply other threads:[~2005-11-06 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 5:21 Paul Jackson
2005-11-06 5:56 ` Hugh Dickins
2005-11-06 6:17 ` Paul Jackson [this message]
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=20051105221728.3fa25f69.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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