From: Ingo Molnar <mingo@chiara.csoma.elte.hu>
To: linux-kernel@vger.rutgers.edu, MM mailing list <linux-mm@kvack.org>
Cc: Linus Torvalds <torvalds@transmeta.com>
Subject: [patch] zoned-2.3.28-J5
Date: Tue, 16 Nov 1999 02:08:04 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.9911160158240.15151-101000@chiara.csoma.elte.hu> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2149 bytes --]
this is zoned-2.3.28-J5, and it should fix all (most) known problems.
Please let me know if the '16MB RAM' case is still problematic. I've
tested it (without swap), and memory balance appears to be just fine.
-- mingo
Changes in zoned-2.3.28-J5:
- further page_alloc.c cleanups/speedups.
- Alan and Rogier convinced me to optimize the 'top level zone is empty'
case a bit more.
- show_free_areas() works again.
- some more include file fixes
Changes in zoned-2.3.28-H2:
- fixed NFS to work out of high memory - tested with moderate load. All
NFS caches (directory, symlink, data, etc.) are in high memory.
- modules fix ...
- page->virtual is filled out for non-highmem pages too, this is a
nice speedup in certain cases.
- fixed a bug in highmem support which might cause user-datapage
corruption in certain cases.
Changes in zoned-2.3.28-G5:
- this one should actually compile if modules support is turned on ...
Changes in zoned-2.3.28-G4:
- implemented 'zone chains' zonelist_t and gfp_mask indexed zonelists[]
speedups (Linus' idea) to handle fallback zones. This should enable
advanced NUMA-style allocations as well. [fallback to different CPUs is
possible via changing build_zonelists().]
- <=16MB RAM boxes should boot just fine now.
- added page->zone for easier deallocation and generic cleanliness. This
also helps NUMA.
- cleaned up the page-allocator namespace, there are only two 'core'
page-allocation functions left: __alloc_pages() and __free_pages_ok().
- modules should compile again.
- we are now inlining the 'put_page_testzero()' part of __free_page_ok.
This is subtle as page->count for reserved pages is now 'rotating' -
this is fine though and lets us to put the rare PageReserved() branch
into __free_page_ok().
- cleaned up pgtable.h, split into lowlevel and highlevel parts, this
fixes dependencies in mm.h & misc.c.
- serial.c didnt clear freshly allocated bootmem - as a result now all
bootmem allocations are explicitly cleared, it's not performance
critical anyway.
- fixed code,data,initmem reporting.
- fixed boot task's swapper_pg_dir clearing
-- mingo
[-- Attachment #2: Type: APPLICATION/OCTET-STREAM, Size: 15904 bytes --]
next reply other threads:[~1999-11-16 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-16 1:08 Ingo Molnar [this message]
1999-11-16 9:47 Ingo Molnar
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=Pine.LNX.4.10.9911160158240.15151-101000@chiara.csoma.elte.hu \
--to=mingo@chiara.csoma.elte.hu \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox