From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.17rc2aa1
Date: Wed, 19 Dec 2001 16:16:10 +0100 [thread overview]
Message-ID: <20011219161610.I1395@athlon.random> (raw)
This should fix the last loop deadlocks under VM pressure, if not please
let me know.
I didn't fixed the ia64 compilation troubles, but it should be very easy
to fix if anybody needs.
URL:
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.17rc2aa1.bz2
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.17rc2aa1/
Only in 2.4.17rc1aa1: 00_loop-deadlock-1
Merged in mainline.
Only in 2.4.17rc2aa1: 00_pgt-cache-leak-1
Avoid potentially leaking pagetables into the per-cpu queues.
Only in 2.4.17rc2aa1: 00_x86-fast-pte-1
Reenable the pagetable per-cpu queues on x86 that I found to be
disabled during 2.4.17pre.
Only in 2.4.17rc1aa1: 10_vm-20
Only in 2.4.17rc2aa1: 10_vm-21
Drop some leftover and rediffed.
Only in 2.4.17rc1aa1: 60_tux-2.4.16-final-D5.bz2
Only in 2.4.17rc2aa1: 60_tux-2.4.16-final-D6.bz2
Latest update from Ingo at www.redhat.com/~mingo/ .
Only in 2.4.17rc2aa1: 70_loop-deadlock-2
Previous fix cured balance_dirty(), this one will cure
the memory balancing, to avoid reentrant I/O in the loop
thread.
Andrea
next reply other threads:[~2001-12-19 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011221025857.M1477@athlon.random>
2001-12-19 15:16 ` Andrea Arcangeli [this message]
2001-12-19 20:32 ` 2.4.17rc2aa1 Gergely Nagy
2001-12-19 20:52 ` 2.4.17rc2aa1 Andrea Arcangeli
2001-12-20 18:17 ` 2.4.17rc2aa1 Gergely Nagy
2001-12-21 19:34 ` 2.4.17rc2aa1 Gergely Nagy
2001-12-20 18:22 ` 2.4.17rc2aa1 Andrea Arcangeli
2001-12-20 18:27 ` 2.4.17rc2aa1 Linus Torvalds
2001-12-20 18:32 ` 2.4.17rc2aa1 Andrea Arcangeli
2001-12-20 18:35 ` 2.4.17rc2aa1 Linus Torvalds
2001-12-20 19:28 ` 2.4.17rc2aa1 Christoph Hellwig
2001-12-25 20:22 ` 2.4.17rc2aa1 - blocking(?) in /proc Adam Schrotenboer
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=20011219161610.I1395@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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.