linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@edgeglobal.com>
To: linux-mm@kvack.org
Subject: mm->mmap_sem
Date: Wed, 22 Sep 1999 17:02:07 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.9909221454320.26444-100000@imperial.edgeglobal.com> (raw)


I noticed that mm_struct has a semaphore in it. How go is it protecting
the memory region? Say we have teh following case. I have a process
that mmaps a chunk of memory and this memory can be sharded with other 
processes. What if the process does a mlock which does a
down(mm->mmap_sem). Now the process goes to sleep and another process
tries to modify the memory region. Will this semaphore protect this
region? In a SMP machine same thing. What kind of protect does this
semaphore provide? Does it prevent other process from doing anything to
the memory. I meant even writing or read it. Thank you.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

             reply	other threads:[~1999-09-22 20:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-22 21:02 James Simmons [this message]
1999-09-24  0:07 ` mm->mmap_sem Stephen C. Tweedie
1999-09-24 14:59   ` mm->mmap_sem James Simmons
1999-09-24 18:09     ` mm->mmap_sem Stephen C. Tweedie
1999-09-25  1:24       ` mm->mmap_sem James Simmons
1999-09-25 14:55         ` mm->mmap_sem Andrea Arcangeli
1999-09-25 16:50           ` mm->mmap_sem James Simmons
1999-09-25 17:06             ` mm->mmap_sem Andrea Arcangeli
1999-09-26  1:19               ` mm->mmap_sem James Simmons
1999-09-26 14:07                 ` mm->mmap_sem Andrea Arcangeli
1999-09-27  8:55                 ` mm->mmap_sem Marcus Sundberg
1999-09-27 19:31                   ` mm->mmap_sem James Simmons
1999-09-29 23:00                     ` mm->mmap_sem Stephen C. Tweedie
1999-09-30  0:17                       ` mm->mmap_sem James Simmons
1999-09-30  0:23                         ` mm->mmap_sem Benjamin C.R. LaHaise
1999-09-30 14:59                           ` mm->mmap_sem James Simmons
1999-09-30 15:15                             ` mm->mmap_sem Benjamin C.R. LaHaise
1999-09-30 16:05                               ` mm->mmap_sem James Simmons
1999-09-30 14:54                         ` mm->mmap_sem Stephen C. Tweedie
1999-09-27 14:16                 ` mm->mmap_sem Stephen C. Tweedie
1999-09-27 20:22                   ` mm->mmap_sem James Simmons
1999-09-27 14:13             ` mm->mmap_sem Stephen C. Tweedie
1999-09-27  8:08     ` mm->mmap_sem Neil Conway

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=Pine.LNX.4.10.9909221454320.26444-100000@imperial.edgeglobal.com \
    --to=jsimmons@edgeglobal.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox