From: "ms" <masp0008@stud.uni-sb.de>
To: linux-mm@kvack.org
Subject: mm synchronization question
Date: Tue, 27 Jul 1999 12:30:39 +0200 [thread overview]
Message-ID: <003101bed81b$1d39dac0$30b16086@sl16es04.phil.uni-sb.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
I think I found a minor bug:
do_wp_page() does not call spin_unlock() if called with bad parameters:
if "goto bad_wp_page" is executed, then noone unlocks the page_table_lock spinlock.
My second question is the mm semaphore:
It seems that if in a multi threaded application several threads access a large mmaped file, that then all page-in operations are serialized (including waiting for the disk IO)
Is that correct?
Are there any plans to change that?
a possible alternative:
* every mm has a linked list of all pages the OS is currently working on.
* instead of just acquiring the mm semaphore, every operation must first check that there are no collisions with pending operations, then it acquires the semaphore.
* we drop the mm semaphore during long (i.e. IO) operations.
Please Cc, I´m currently not on the mailing list.
--
Manfred
[-- Attachment #2: Type: text/html, Size: 2216 bytes --]
next reply other threads:[~1999-07-27 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-27 10:30 ms [this message]
1999-07-28 4:34 ` [PATCH] " Stephen C. Tweedie
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='003101bed81b$1d39dac0$30b16086@sl16es04.phil.uni-sb.de' \
--to=masp0008@stud.uni-sb.de \
--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