From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.18rc4aa1
Date: Sun, 24 Feb 2002 16:55:31 +0100 [thread overview]
Message-ID: <20020224165531.A14179@dualathlon.random> (raw)
URL:
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.18rc4aa1.gz
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.18rc4aa1/
Only in 2.4.18rc2aa2: 00_block-highmem-all-18b-2.gz
Only in 2.4.18rc4aa1: 00_block-highmem-all-18b-3.gz
Only in 2.4.18rc2aa2: 10_block-highmem-all-18b-2
Don't mark it experimental anymore and avoid changing the ll_rw_block
queue changes in this patch, return to the mainline values. If needed
they should go into a separate patch for clarity.
Use CONFIG_DISCONTIGMEM for some microoptimization.
Only in 2.4.18rc4aa1: 00_prepare-write-fixes-1
Fixed a few bugs in the block_prepare_write while dealing with
get_block failures.
Only in 2.4.18rc2aa2: 00_ptrace-fix-1
Merged in mainline.
Only in 2.4.18rc2aa2: 10_vm-25
Only in 2.4.18rc4aa1: 10_vm-27
Further updates.
Only in 2.4.18rc2aa2: 20_balance-dirty-wait-1
Dropped (to see if write performance increases).
Only in 2.4.18rc2aa2: 20_pte-highmem-13
Only in 2.4.18rc4aa1: 20_pte-highmem-14
Merged ia64.
Only in 2.4.18rc4aa1: 70_xfs-1.gz
Merged SGI's XFS integrated with -aa VM.
Andrea
next reply other threads:[~2002-02-24 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-24 15:55 Andrea Arcangeli [this message]
2002-02-24 21:25 ` 2.4.18rc4aa1 Diego Calleja
2002-02-24 20:34 ` 2.4.18rc4aa1 Eric Krout
2002-02-24 21:28 ` 2.4.18rc4aa1 Allan Sandfeld
2002-02-24 23:08 ` 2.4.18rc4aa1 Diego Calleja
2002-02-25 12:50 ` 2.4.18rc4aa1 Andrea Arcangeli
2002-02-25 14:41 ` 2.4.18rc4aa1 H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2002-02-24 21:29 2.4.18rc4aa1 rwhron
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=20020224165531.A14179@dualathlon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).