From: Andrew Morton <akpm@zip.com.au>
To: lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: MM patches against 2.5.31
Date: Wed, 21 Aug 2002 19:29:04 -0700 [thread overview]
Message-ID: <3D644C70.6D100EA5@zip.com.au> (raw)
I've uploaded a rollup of pending fixes and feature work
against 2.5.31 to
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.31/2.5.31-mm1/
The rolled up patch there is suitable for ongoing testing and
development. The individual patches are in the broken-out/
directory and should all be documented.
broken-out/linus.patch
Incremental BK patch from Linus' tree
broken-out/page_reserved.patch
Test PageReserved in pagevec_release()
broken-out/scsi_hack.patch
Fix block-highmem for scsi
broken-out/page_cache_release_lru_fix.patch
Fix a race between __page_cache_release() and shrink_cache().
broken-out/page_cache_release_fix.patch
Fix __page_cache_release() bugs
broken-out/mvm.patch
Fix vmalloc bugs
broken-out/pte-chain-fix.patch
Fix a VM lockup on uniprocessors
broken-out/func-fix.patch
gcc-2.91.66 does not support __func__
broken-out/ext3-htree.patch
Indexed directories for ext3
broken-out/rmap-mapping-BUG.patch
Fix a BUG_ON(page->mapping == NULL) in try_to_unmap()
broken-out/misc.patch
misc fixlets
broken-out/tlb-speedup.patch
Reduce typical global TLB invalidation frequency by 35%
broken-out/buffer-slab-align.patch
Don't align the buffer_head slab on hardware cacheline boundaries
broken-out/zone-rename.patch
Rename zone_struct->zone, zonelist_struct->zonelist. Remove zone_t,
zonelist_t.
broken-out/per-zone-lru.patch
Per-zone page LRUs
broken-out/per-zone-lock.patch
Per-zone LRU list locking
broken-out/l1-max-size.patch
Infrastructure for determining the maximum L1 cache size which the kernel
may have to support.
broken-out/zone-lock-alignment.patch
Pad struct zone to ensure that the lru and buddy locks are in separate
cachelines.
broken-out/put_page_cleanup.patch
Clean up put_page() and page_cache_release().
broken-out/anon-batch-free.patch
Batched freeing and de-LRUing of anonymous pages
broken-out/writeback-sync.patch
Writeback fixes and tuneups
broken-out/ext3-inode-allocation.patch
Fix an ext3 deadlock
broken-out/ext3-o_direct.patch
O_DIRECT support for ext3.
broken-out/jfs-bio.patch
Convert JFS to use direct-to-BIO I/O
broken-out/discontig-paddr_to_pfn.patch
Convert page pointers into pfns for i386 NUMA
broken-out/discontig-setup_arch.patch
Rework setup_arch() for i386 NUMA
broken-out/discontig-mem_init.patch
Restructure mem_init for i386 NUMA
broken-out/discontig-i386-numa.patch
discontigmem support for i386 NUMA
broken-out/cleanup-mem_map-1.patch
Clean up lots of open-coded uese of mem_map[]. For ia32 NUMA
broken-out/zone-pages-reporting.patch
Fix the boot-time reporting of each zone's available pages
broken-out/enospc-recovery-fix.patch
Fix the __block_write_full_page() error path.
broken-out/fix-faults.patch
Back out the initial work for atomic copy_*_user()
broken-out/bkl-consolidate.patch
Consolidation per-arch lock_kenrel() implementations.
broken-out/might_sleep.patch
Infrastructure to detect sleep-inside-spinlock bugs
broken-out/spin-lock-check.patch
spinlock/rwlock checking infrastructure
broken-out/atomic-copy_user.patch
Support for atomic copy_*_user()
broken-out/kmap_atomic_reads.patch
Use kmap_atomic() for generic_file_read()
broken-out/kmap_atomic_writes.patch
Use kmap_atomic() for generic_file_write()
broken-out/config-PAGE_OFFSET.patch
Configurable kenrel/user memory split
broken-out/throttling-fix.patch
Fix throttling of heavy write()rs.
broken-out/dirty-state-accounting.patch
Make the global dirty memory accounting more accurate
broken-out/rd-cleanup.patch
Cleanup and fix the ramdisk driver (doesn't work right yet)
--
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/
next reply other threads:[~2002-08-22 2:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 2:29 Andrew Morton [this message]
2002-08-22 11:28 ` Christian Ehrhardt
2002-08-26 1:52 ` Andrew Morton
2002-08-26 9:10 ` Christian Ehrhardt
2002-08-26 14:22 ` Daniel Phillips
2002-08-26 15:29 ` Christian Ehrhardt
2002-08-26 17:56 ` Daniel Phillips
2002-08-26 19:24 ` Andrew Morton
2002-08-26 19:34 ` Daniel Phillips
2002-08-26 19:48 ` Christian Ehrhardt
2002-08-27 9:22 ` Christian Ehrhardt
2002-08-27 19:19 ` Andrew Morton
2002-08-26 20:00 ` Christian Ehrhardt
2002-08-26 20:09 ` Daniel Phillips
2002-08-26 20:58 ` Christian Ehrhardt
2002-08-27 16:48 ` Daniel Phillips
2002-08-28 13:14 ` Christian Ehrhardt
2002-08-28 17:18 ` Daniel Phillips
2002-08-28 17:42 ` Andrew Morton
2002-08-28 20:41 ` Daniel Phillips
2002-08-28 21:03 ` Andrew Morton
2002-08-28 22:04 ` Daniel Phillips
2002-08-28 22:39 ` Andrew Morton
2002-08-28 22:57 ` Daniel Phillips
2002-08-26 21:31 ` Andrew Morton
2002-08-27 3:42 ` Benjamin LaHaise
2002-08-27 4:37 ` Andrew Morton
2002-08-22 15:59 ` Steven Cole
2002-08-22 16:06 ` Martin J. Bligh
2002-08-22 19:45 ` Steven Cole
2002-08-26 2:15 ` Andrew Morton
2002-08-26 2:08 ` Martin J. Bligh
2002-08-26 2:32 ` Andrew Morton
2002-08-26 3:06 ` Steven Cole
2002-08-26 22:09 Ed Tomlinson
2002-08-26 23:58 ` Andrew Morton
2002-08-27 0:13 ` Rik van Riel
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=3D644C70.6D100EA5@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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