From: Andrea Arcangeli <andrea@e-mind.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Zlatko.Calusic@CARNet.hr, Linux-MM List <linux-mm@kvack.org>,
Andi Kleen <andi@zero.aec.at>
Subject: Re: Update shared mappings
Date: Wed, 2 Dec 1998 19:32:56 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.3.96.981202191811.4720A-100000@dragon.bogus> (raw)
In-Reply-To: <199812021621.QAA04235@dax.scot.redhat.com>
On Wed, 2 Dec 1998, Stephen C. Tweedie wrote:
>else's mm semaphore. If you have two processes doing that to each other
>(ie. two processes mapping the same file r/w and doing msyncs), then you
>can most certainly still deadlock.
The thing would be trivially fixable if it would exists a down_trylock()
that returns 0 if the semaphore was just held. I rejected now the
update_shared_mappings from my tree in the meantime though.
I have a question. Please consider only the UP case (as if linux would not
support SMP at all). Is it possible that while we are running inside
sys_msync() and another process has the mmap semaphore held?
Stephen I read some emails about a PG_dirty flag. Could you tell me some
more about that flag?
Andrea Arcangeli
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-12-02 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-20 4:10 Zlatko Calusic
1998-11-30 13:52 ` Stephen C. Tweedie
1998-11-30 15:19 ` Zlatko Calusic
1998-11-30 20:02 ` Andrea Arcangeli
1998-12-01 15:03 ` Stephen C. Tweedie
1998-12-01 17:48 ` Andrea Arcangeli
1998-12-02 16:21 ` Stephen C. Tweedie
1998-12-02 18:32 ` Andrea Arcangeli [this message]
1998-12-03 5:44 ` Eric W. Biederman
1998-12-03 11:56 ` 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=Pine.LNX.3.96.981202191811.4720A-100000@dragon.bogus \
--to=andrea@e-mind.com \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=andi@zero.aec.at \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
/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