From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Rik van Riel <riel@conectiva.com.br>,
linux-mm@kvack.org
Subject: Re: page_table_lock problem [was: Re: 2.4 / 2.5 VM plans]
Date: Thu, 6 Jul 2000 14:32:51 +0100 [thread overview]
Message-ID: <20000706143251.C4237@redhat.com> (raw)
In-Reply-To: <20000706155123.A11504@saw.sw.com.sg>; from saw@saw.sw.com.sg on Thu, Jul 06, 2000 at 03:51:23PM +0800
Hi,
On Thu, Jul 06, 2000 at 03:51:23PM +0800, Andrey Savochkin wrote:
>
> I've looked at RSS updates in 2.4.0 kernels.
> You're right, they are not protected enough from
> concurrent updates from mm paths (mmap, page fault handler) and swapout
> path. Moreover, I found that page_table_lock which is supposed to serialize
> page table updates from mm and swapout paths isn't taken in the later at all!
> Is it a bug or am I missing something?
Sorry, I don't have time to look closely at this right now --- I'm
swamped with travel and ext3 work, and I've just moved house...
Cheers,
Stephen
--
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.eu.org/Linux-MM/
prev parent reply other threads:[~2000-07-06 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-25 3:51 2.4 / 2.5 VM plans Rik van Riel
2000-06-28 17:45 ` vii
2000-06-28 21:04 ` Juan J. Quintela
2000-06-28 21:17 ` Juan J. Quintela
2000-06-29 13:45 ` Stephen C. Tweedie
2000-06-29 13:44 ` Stephen C. Tweedie
2000-07-06 7:51 ` page_table_lock problem [was: Re: 2.4 / 2.5 VM plans] Andrey Savochkin
2000-07-06 13:32 ` Stephen C. Tweedie [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=20000706143251.C4237@redhat.com \
--to=sct@redhat.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=saw@saw.sw.com.sg \
/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