From: Andrea Arcangeli <andrea@e-mind.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Neil Booth <NeilB@earthling.net>,
linux-mm@kvack.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: A couple of questions
Date: Tue, 16 Mar 1999 03:11:25 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.05.9903160239270.360-100000@laser.random> (raw)
In-Reply-To: <199903151858.SAA02057@dax.scot.redhat.com>
On Mon, 15 Mar 1999, Stephen C. Tweedie wrote:
>--- mm/memory.c~ Tue Jan 19 01:33:10 1999
>+++ mm/memory.c Mon Mar 15 18:57:31 1999
>@@ -651,13 +651,13 @@
> delete_from_swap_cache(page_map);
> /* FallThrough */
> case 1:
>- /* We can release the kernel lock now.. */
>- unlock_kernel();
>-
> flush_cache_page(vma, address);
> set_pte(page_table, pte_mkdirty(pte_mkwrite(pte)));
> flush_tlb_page(vma, address);
> end_wp_page:
>+ /* We can release the kernel lock now.. */
>+ unlock_kernel();
>+
> if (new_page)
> free_page(new_page);
> return 1;
>----------------------------------------------------------------
Your sure safe patch is strictly needed according to me in order to
release the lock_kernel in the end_wp_page path.
The reason I think it's just safe remove the lock_kernel before updating
the page table of the process is because the swap_out engine will do
nothing with the page until it will be a clean page (and should be clean
because it was read-only in first place.... am I really right here?).
Every other part of the VM will block on the semaphore so it won't race
anyway with the page fault handler.
I think this patch against 2.2.3 looks needed to me (except the first
chunk that is only removing superflous code).
Seems to works fine after some minute of stress-testing.
Index: mm//memory.c
===================================================================
RCS file: /var/cvs/linux/mm/memory.c,v
retrieving revision 1.1.2.3
diff -u -r1.1.2.3 memory.c
--- memory.c 1999/01/24 02:46:31 1.1.2.3
+++ linux/mm/memory.c 1999/03/16 01:55:45
@@ -624,10 +624,6 @@
/* Did someone else copy this page for us while we slept? */
if (pte_val(*page_table) != pte_val(pte))
goto end_wp_page;
- if (!pte_present(pte))
- goto end_wp_page;
- if (pte_write(pte))
- goto end_wp_page;
old_page = pte_page(pte);
if (MAP_NR(old_page) >= max_mapnr)
goto bad_wp_page;
@@ -651,13 +647,18 @@
delete_from_swap_cache(page_map);
/* FallThrough */
case 1:
- /* We can release the kernel lock now.. */
+ /*
+ * We can release the kernel lock now.. because the swap_out
+ * engine will do nothing with the page table until it
+ * will be a clean page (and we are sure it's clean because it
+ * wasn't writable yet). All other parts of the VM will
+ * stop on the mmap semaphore. -arca
+ */
unlock_kernel();
flush_cache_page(vma, address);
set_pte(page_table, pte_mkdirty(pte_mkwrite(pte)));
flush_tlb_page(vma, address);
-end_wp_page:
if (new_page)
free_page(new_page);
return 1;
@@ -681,9 +682,15 @@
bad_wp_page:
printk("do_wp_page: bogus page at address %08lx (%08lx)\n",address,old_page);
send_sig(SIGKILL, tsk, 1);
+ unlock_kernel();
if (new_page)
free_page(new_page);
return 0;
+end_wp_page:
+ unlock_kernel();
+ if (new_page)
+ free_page(new_page);
+ return 1;
}
/*
Andrea Arcangeli
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-03-16 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-02 13:11 Neil Booth
1999-03-15 18:58 ` Stephen C. Tweedie
1999-03-15 22:46 ` neil
1999-03-16 12:22 ` Stephen C. Tweedie
1999-03-16 2:11 ` Andrea Arcangeli [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.05.9903160239270.360-100000@laser.random \
--to=andrea@e-mind.com \
--cc=NeilB@earthling.net \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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