From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: ak@suse.de, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] Fold numa_maps into mempolicy.c
Date: Tue, 15 Nov 2005 23:10:51 -0800 [thread overview]
Message-ID: <20051115231051.5437e25b.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0511081524570.32262@schroedinger.engr.sgi.com>
Christoph wrote:
> + * Must hold mmap_sem until memory pointer is no longer in use
> + * or be called from the current task.
> + */
> +struct mempolicy *get_vma_policy(struct task_struct *task,
Twenty (well, four) questions time.
Hmmm ... is that true - that get_vma_policy() can be called for the
current task w/o holding mmap_sem?
Is there any call to get_vma_policy() made that isn't holding mmap_sem?
Except for /proc output, is there any call to get_vma_policy made on any
task other than current?
What does "until memory pointer is no longer in use" mean?
--
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>
next prev parent reply other threads:[~2005-11-16 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 23:24 [PATCH 1/2] private pointer in check_range and MPOL_MF_INVERT Christoph Lameter
2005-11-08 23:25 ` [PATCH 2/2] Fold numa_maps into mempolicy.c Christoph Lameter
2005-11-16 7:10 ` Paul Jackson [this message]
2005-11-16 8:36 ` Andi Kleen
2005-11-16 18:54 ` Christoph Lameter
2005-11-16 19:43 ` Paul Jackson
2005-11-16 18:21 ` Christoph Lameter
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=20051115231051.5437e25b.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=clameter@engr.sgi.com \
--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 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.