public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Andrew Morton <andrewm@uow.edu.au>
Subject: 2.4.17rc1aa1
Date: Fri, 14 Dec 2001 18:14:44 +0100	[thread overview]
Message-ID: <20011214181444.B2431@athlon.random> (raw)

Marcelo, can you merge the loop-deadlock fix? (the others aren't
trivially mergeable yet and for the tcp conntrack you'd need to ask
Rusty first, the change is simple enough that I merged it for now)

Andrew, could you give it a spin to verify I/O performance is back? It
is fast for me now.

URL:

	ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.17rc1aa1.bz2
	ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.17rc1aa1/

Only in 2.4.17rc1aa1: 00_block-highmem-all-18b-2.bz2
Only in 2.4.17pre4aa1: 00_block-highmem-all-18b.bz2
Only in 2.4.17pre4aa1: 00_flush_icache_range-1
Only in 2.4.17rc1aa1: 00_flush_icache_range-2
Only in 2.4.17pre4aa1: 00_silent-stack-overflow-12
Only in 2.4.17rc1aa1: 00_silent-stack-overflow-13
Only in 2.4.17pre4aa1: 00_spinlock-cacheline-2
Only in 2.4.17rc1aa1: 00_spinlock-cacheline-3
Only in 2.4.17pre4aa1: 10_numa-sched-14
Only in 2.4.17rc1aa1: 10_numa-sched-15
Only in 2.4.17pre4aa1: 60_atomic-alloc-6
Only in 2.4.17rc1aa1: 60_atomic-alloc-7

	Rediffed.

Only in 2.4.17pre4aa1: 00_rwsem-fair-25-recursive-6
Only in 2.4.17rc1aa1: 00_rwsem-fair-25-recursive-7

	Not used actively anymore for the coredump (we walk the pagetables
	by hand instead of using the MMU now).

Only in 2.4.17rc1aa1: 00_loop-deadlock-1

	Fixed loop deadlock (balance_dirty() must not be called within the
	request_fn or it can deadlock or recurse way too much). It is
	enough to recall balance_dirty() at the highest layer so this won't
	introduce any stability problem.

Only in 2.4.17rc1aa1: 00_tcp-conntrack-fin-1

	After upgrading my firewall/NAT to 2.4 (s/ipchains/iptables/ :) I started
	getting valid tcp packets dropped/logged (I'm allowing only RELATED and
	ESTABLISHED packets from the outside, with ipchains I was allowing all
	tcp packets that weren't syn and there weren't problems). Rusty sent me
	the above fix to see if my problem with the tcp connection tracking
	goes away (without adding again the rule that all non tcp syn can came in).

Only in 2.4.17pre4aa1: 10_vm-19
Only in 2.4.17rc1aa1: 10_vm-20

	Should fix the I/O async flushing performance drop reported by Andrew.
	Cannot += BUF_LOCKED any longer in balance_dirty because we don't waste
	time any longer refiling clean buffers into the BUF_CLEAN now (sync has to
	pass all over the bh anyways so it doesn't matter for it either).
	Avoid collapsing the max_mapped during shrink_cache internal passes.

Only in 2.4.17pre4aa1: 50_uml-patch-2.4.15-3.bz2
Only in 2.4.17rc1aa1: 50_uml-patch-2.4.16-2.bz2

	Latest update from Jeff at user-mode-linux.sourceforge.net.

Only in 2.4.17pre4aa1: 60_tux-2.4.16-final-C9.bz2
Only in 2.4.17rc1aa1: 60_tux-2.4.16-final-D5.bz2

	Latest update from Ingo at www.redhat.com/~mingo/.

Andrea

             reply	other threads:[~2001-12-14 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-14 17:14 Andrea Arcangeli [this message]
2001-12-14 21:24 ` Another loop bug? (Was: 2.4.17rc1aa1) Gergely Nagy
2001-12-15  4:52 ` 2.4.17rc1aa1 Barry K. Nathan
2001-12-17 15:33   ` 2.4.17rc1aa1 Andrea Arcangeli

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=20011214181444.B2431@athlon.random \
    --to=andrea@suse.de \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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