From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: steve@digidescorp.com, gerg@snapgear.com, stable@kernel.org
Subject: + nommu-yield-cpu-while-disposing-vm.patch added to -mm tree
Date: Tue, 16 Nov 2010 12:26:00 -0800 [thread overview]
Message-ID: <201011162026.oAGKQ1ke005706@imap1.linux-foundation.org> (raw)
The patch titled
nommu: yield CPU while disposing VM
has been added to the -mm tree. Its filename is
nommu-yield-cpu-while-disposing-vm.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: nommu: yield CPU while disposing VM
From: "Steven J. Magnani" <steve@digidescorp.com>
Depending on processor speed, page size, and the amount of memory a
process is allowed to amass, cleanup of a large VM may freeze the system
for many seconds. This can result in a watchdog timeout.
Make sure other tasks receive some service when cleaning up large VMs.
Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
Cc: Greg Ungerer <gerg@snapgear.com>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/nommu.c | 1 +
1 file changed, 1 insertion(+)
diff -puN mm/nommu.c~nommu-yield-cpu-while-disposing-vm mm/nommu.c
--- a/mm/nommu.c~nommu-yield-cpu-while-disposing-vm
+++ a/mm/nommu.c
@@ -1717,6 +1717,7 @@ void exit_mmap(struct mm_struct *mm)
mm->mmap = vma->vm_next;
delete_vma_from_mm(vma);
delete_vma(mm, vma);
+ cond_resched();
}
kleave("");
_
Patches currently in -mm which might be from steve@digidescorp.com are
nommu-yield-cpu-while-disposing-vm.patch
reply other threads:[~2010-11-16 20:27 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=201011162026.oAGKQ1ke005706@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=stable@kernel.org \
--cc=steve@digidescorp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.