From: Linus Torvalds <torvalds@transmeta.com>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: Linux-MM@kvack.org, number6@the-village.bc.nu
Subject: Re: [PATCH] kanoj-mm2.0-2.2.9 unneccesary page force in by munlock
Date: Sun, 16 May 1999 21:48:03 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.3.95.990516214528.4550B-100000@penguin.transmeta.com> (raw)
In-Reply-To: <199905170402.VAA25069@google.engr.sgi.com>
On Sun, 16 May 1999, Kanoj Sarcar wrote:
>
> While looking at the code for munlock() in mm/mlock.c, I found
> that munlock() unneccesarily executes a code path that forces
> page fault in over the entire range. The following patch fixes
> this problem:
Well, it shouldn't force a page-fault, as the code is only executed if the
lockedness changes - and if it is a unlock then it will have been locked
before, so all the pages will have been present, and as such we wouldn't
actually need to fault them in.
I agree that it is certainly unnecessary, though, and pollutes TLB's etc
for no good reason.
How about this diff instead, avoiding the if-then-else setup?
Linus
-----
--- v2.3.2/linux/mm/mlock.c Fri Nov 20 11:43:19 1998
+++ linux/mm/mlock.c Sun May 16 21:45:23 1999
@@ -115,10 +115,11 @@
if (!retval) {
/* keep track of amount of locked VM */
pages = (end - start) >> PAGE_SHIFT;
- if (!(newflags & VM_LOCKED))
+ if (newflags & VM_LOCKED) {
pages = -pages;
- vma->vm_mm->locked_vm += pages;
- make_pages_present(start, end);
+ make_pages_present(start, end);
+ }
+ vma->vm_mm->locked_vm -= pages;
}
return retval;
}
--
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/
next prev parent reply other threads:[~1999-05-17 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-17 4:02 Kanoj Sarcar
1999-05-17 4:48 ` Linus Torvalds [this message]
1999-05-17 6:16 ` Kanoj Sarcar
1999-05-17 16:11 ` Linus Torvalds
1999-05-17 17:31 ` Kanoj Sarcar
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.95.990516214528.4550B-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=Linux-MM@kvack.org \
--cc=kanoj@google.engr.sgi.com \
--cc=number6@the-village.bc.nu \
/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