linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, Robert Love <rml@tech9.net>
Subject: Re: [PATCH](3/2) rmap14 for ac  (was: Re: 2.5.34-mm4)
Date: Mon, 16 Sep 2002 00:07:58 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.44L.0209160005230.1857-100000@imladris.surriel.com> (raw)

Hi,

as an added bonus, here is patch 3 out of 2, with a small
SMP bugfix. It turned out Arjan's patch for rmap14 wasn't
safe as vmtruncate calls zap_page_range while holding a
spinlock.  Guess I'll have to release rmap14b soon ;)

Rik
-- 
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/		http://distro.conectiva.com/
Spamtraps of the month:  september@surriel.com trac@trac.org


# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.688   -> 1.689
#	         mm/memory.c	1.56    -> 1.57
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/09/16	riel@imladris.surriel.com	1.689
# vmtruncate calls zap_page_range() with a spinlock held, so remove
# the explicit low latency schedule -- rml
# --------------------------------------------
#
diff -Nru a/mm/memory.c b/mm/memory.c
--- a/mm/memory.c	Mon Sep 16 00:05:15 2002
+++ b/mm/memory.c	Mon Sep 16 00:05:15 2002
@@ -436,9 +436,6 @@

 		spin_unlock(&mm->page_table_lock);

-		if (current->need_resched)
-			schedule();
-
 		address += block;
 		size -= block;
 	}

--
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-mm.org/

                 reply	other threads:[~2002-09-16  3:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.44L.0209160005230.1857-100000@imladris.surriel.com \
    --to=riel@conectiva.com.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rml@tech9.net \
    /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