From: Rik van Riel <riel@conectiva.com.br>
To: Andrew Morton <akpm@zip.com.au>
Cc: Robert Love <rml@tech9.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] low-latency zap_page_range()
Date: Thu, 29 Aug 2002 18:46:15 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44L.0208291845060.1857-100000@imladris.surriel.com> (raw)
In-Reply-To: <3D6E9084.820B2608@zip.com.au>
On Thu, 29 Aug 2002, Andrew Morton wrote:
> > So we know it is held forever and a day... but is there contention?
>
> I'm sure there is, but nobody has measured the right workload.
>
> Two CLONE_MM threads, one running mmap()/munmap(), the other trying
> to fault in some pages. I'm sure someone has some vital application
> which does exactly this. They always do :(
Can't fix this one. The mmap()/munmap() needs to have the
mmap_sem for writing as long as its setting up or tearing
down a VMA while the pagefault path takes the mmap_sem for
reading.
It might be fixable in some dirty way, but I doubt that'll
ever be worth it.
regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
--
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/
prev parent reply other threads:[~2002-08-29 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 15:31 Robert Love
2002-08-29 20:30 ` Andrew Morton
2002-08-29 20:40 ` Robert Love
2002-08-29 20:46 ` Robert Love
2002-08-29 20:59 ` Andrew Morton
2002-08-29 21:38 ` William Lee Irwin III
2002-08-29 21:00 ` Andrew Morton
2002-08-29 21:12 ` Robert Love
2002-08-29 21:22 ` Andrew Morton
2002-08-29 21:46 ` Rik van Riel [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=Pine.LNX.4.44L.0208291845060.1857-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rml@tech9.net \
/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