On Fri, 13 Apr 2007, Yasunori Goto wrote:
Hello.
cmdline_parse_kernelcore() should return the next pointer of boot option
like memparse() doing. If not, it is cause of eternal loop on ia64 box.
This patch is for 2.6.21-rc6-mm1.
Signed-off-by: Yasunori Goto [EMAIL PROTECTED]
Acked-by: Mel
(),
page_group_by_mobility_disabled ? off : on,
vm_total_pages);
+#else
+ printk(Built %i zonelists. Total pages: %ld\n,
+ num_online_nodes(), vm_total_pages);
+#endif
}
/*
--
Pierre
--
Mel Gorman
Part-time Phd Student Linux
);
page = NULL;
-
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick
the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University
@@ extern int ramfs_nommu_mmap(struct file
#endif
extern const struct file_operations ramfs_file_operations;
+extern const struct file_operations ramfs_file_higher_order_operations;
extern struct vm_operations_struct generic_file_vm_ops;
extern int __init init_rootfs(void);
--
Mel
this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
--
Mel Gorman
Part-time Phd Student Linux Technology Center
-movable pages towards the
lower PFNs. Assuming it had a reasonable level of success, even high-order
ramfs pages that were unmovable should work out.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software
. It's nasty looking because sizing the portion of
memory usable by any allocation so that it is evenly spread throughout all
nodes is not trivial. I think that having mem= parsing broken on NUMA at
various times in the past (and probably still broken) highlights that.
--
Mel Gorman
Part-time
so that is compatible with both early_param() way of doing
things and IA64.
[EMAIL PROTECTED]: Fix parsing kernelcore boot option V1]
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.21-rc6-mm1-001_latest/arch/i386/kernel/setup.c
linux-2.6.21
On (23/04/07 19:32), Mel Gorman didst pronounce:
There
was a second problem that showed up while testing this in relation to the
bootmem allocator assumptions about zone boundary alignment. I'll follow up
this mail with the patch in case you are seeing that problem.
Tony Luck added to cc
that is easily avoided.
Bye.
Thanks
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
to a boundary. This patch aligns the zone to a MAX_ORDER_NR_PAGES boundary.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.21-rc6-mm1-002_commonparse/mm/page_alloc.c
linux-2.6.21-rc6-mm1-003_alignmovable/mm/page_alloc.c
--- linux-2.6.21-rc6-mm1
on most test machines.
In combination with the align-zone_movable-to-maxordernrpages-boundary
patch, x86_64, ppc64 and IA64 test machines all booted successfully with
and without kernelcore= specified.
Acked-by: Mel Gorman [EMAIL PROTECTED]
I'll resend the two relevant patches for this problem
on the freelists for the wrong zone resulting in a BUG() later. Aligning
ZONE_MOVABLE avoids the problem.
They have been successfully boot-tested with and without kernelcore=
specified on x86_64, ppc64 and IA64 (where the bug was first triggered).
--
Mel Gorman
Part-time Phd Student
-memory-at-boot-time.patch
x86_64-specify-amount-of-kernel-memory-at-boot-time.patch
x86-specify-amount-of-kernel-memory-at-boot-time.patch
Signed-off-by: Yasunori Goto [EMAIL PROTECTED]
Acked-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Andy Whitcroft [EMAIL PROTECTED]
---
arch/i386/kernel
requested instead
of smaller. The impact is that the kernel-usable portion of memory because a
minimum guarantee instead of the exact size requested by the user.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Andy Whitcroft [EMAIL PROTECTED]
---
page_alloc.c |5 +
1 files changed, 5
On (08/03/07 08:48), Christoph Lameter didst pronounce:
On Thu, 8 Mar 2007, Mel Gorman wrote:
On x86_64, it completed successfully and looked reliable. There was a 5%
performance loss on kernbench and aim9 figures were way down. However, with
slub_debug enabled, I would expect that so
On Thu, 8 Mar 2007, Christoph Lameter wrote:
On Thu, 8 Mar 2007, Mel Gorman wrote:
Note that the 16kb page size has a major
impact on SLUB performance. On IA64 slub will use only 1/4th the locking
overhead as on 4kb platforms.
It'll be interesting to see the kernbench tests
be avoided by using kmalloc.
Yuck! Hopefully your patches fix that fundamental problem.
One way to find out for sure.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from
Note that I am amazed that the kernbench even worked.
The results without slub_debug were not good except for IA64. x86_64 and
ppc64 both blew up for a variety of reasons. The IA64 results were
KernBench Comparison
2.6.21-rc2-mm2-clean
for
the section.
Signed-off-by: Bob Picco [EMAIL PROTECTED]
Signed-off-by: Andy Whitcroft [EMAIL PROTECTED]
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
include/linux/mmzone.h |6 --
mm/sparse.c| 49 ++---
2 files changed, 50 insertions
[EMAIL PROTECTED]
Cc: linux-kernel@vger.kernel.org, Mel Gorman [EMAIL PROTECTED]
Subject: [PATCH] fix BUG_ON check at move_freepages() (Re: 2.6.21-rc3-mm2)
Hello.
The BUG_ON() check at move_freepages() is wrong.
Its end_page is start_page + MAX_ORDER_NR_PAGES. So, it can be
next zone. BUG_ON
and all the data migrated. hmm
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On (14/03/07 09:11), Bjorn Helgaas didst pronounce:
On Wednesday 14 March 2007 03:44, Mel Gorman wrote:
Please try the following patch from Yasunori Goto.
...
--- current_test.orig/mm/page_alloc.c 2007-03-08 15:44:10.0
+0900
+++ current_test/mm/page_alloc.c2007-03-08
to assume the accounting cost.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On (14/03/07 10:52), Bjorn Helgaas didst pronounce:
On Wednesday 14 March 2007 10:13, Mel Gorman wrote:
Ok. This looks like another case of HOLES_IN_ZONE hilarity with page_zone().
As I take a new look at the BUG_ON check in move_freepages(), it isn't even
necessary as move_freepages_block
On Wed, 14 Mar 2007, Bjorn Helgaas wrote:
On Wednesday 14 March 2007 11:21, Mel Gorman wrote:
Can you tell me if the faulting line was at the check for PageBuddy?
I don't know, sorry.
No problem, the fact the patch booted lets me know that calling
PageBuddy() on an invalid page had
CONFIG_HOLES_IN_ZONE and checks
pfn_valid() earlier before calling PageBuddy(). It applies on top of
move-free-pages-between-lists-on-steal-fix-2.patch from Yasunori Goto in -mm.
Credit to Bjorn Helgaas for reporting this bug and testing.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
page_alloc.c | 18
On Wed, 14 Mar 2007, Bjorn Helgaas wrote:
On Wednesday 14 March 2007 12:59, Mel Gorman wrote:
SNIP
Virtual mem_map starts at 0xa0007fffc720
Zone PFN ranges:
Total aside, a message should have been printed out here with
sizeof(struct page) = ?? when loglevel was set to 8. I wanted it so I
/
--
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
even though I think it will
lower success rates for superpage allocations because of increased
fragmentation. Benchmarking will tell me for sure.
Thanks Mariusz for the report.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick
++--
3 files changed, 67 insertions(+), 22 deletions(-)
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.21-rc3-mm2-clean/include/linux/mmzone.h
linux-2.6.21-rc3-mm2-blockreserve/include/linux/mmzone.h
--- linux-2.6.21
today.
Thanks a million for testing.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
MIGRATE_HIGHALLOC and see if the reports stay missing.
Credit to Mariusz Kozlowski for discovering the problem, describing the
failure scenario and testing patches and scenarios.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Andy Whitcroft [EMAIL PROTECTED]
include/linux/mmzone.h |4
On Sun, 18 Mar 2007, Andrew Morton wrote:
On Sat, 17 Mar 2007 18:26:41 + [EMAIL PROTECTED] (Mel Gorman) wrote:
I still haven't got onto reviewing all your mm patches :(
There are a lot them admittadly.
Nor has anyone else, afaik.
They have been reviewed at various points
On Sun, 18 Mar 2007, Andrew Morton wrote:
On Sun, 18 Mar 2007 11:35:36 + (GMT) Mel Gorman [EMAIL PROTECTED] wrote:
But let me leap ahead of myself.
CONFIG_PAGE_GROUP_BY_MOBILITY
Why does this config item exist? It's not good to have some mysterious
knob which affects mm behaviour
On Sun, 18 Mar 2007, Andrew Morton wrote:
On Sun, 18 Mar 2007 19:05:41 + (GMT) Mel Gorman [EMAIL PROTECTED] wrote:
How much additional memory consumption are we expecting here?
Short answer, about 1.5KB on a 1GB system of which 1.3KB is statically
defined in the 3 struct zones on a 1
On Sun, 18 Mar 2007, Andrew Morton wrote:
On Sun, 18 Mar 2007 20:08:49 + (GMT) Mel Gorman [EMAIL PROTECTED] wrote:
On Sun, 18 Mar 2007, Andrew Morton wrote:
On Sun, 18 Mar 2007 19:05:41 + (GMT) Mel Gorman [EMAIL PROTECTED] wrote:
How much additional memory consumption are we
On (14/03/07 13:42), Dave Hansen didst pronounce:
On Wed, 2007-03-14 at 15:38 +, Mel Gorman wrote:
On (13/03/07 10:05), Dave Hansen didst pronounce:
How do we determine what is shared, and goes into the shared zones?
Assuming we had a means of creating a zone that was assigned
(or maybe just give hints) which page size
to use for this mapping.
If a driver wants to tell what pagesize to use, they can override the ops
to call the appropriate hugetlb code. Hints will be damn near impossible to
get right in all cases.
--
Mel Gorman
Part-time Phd Student
On Thu, 22 Mar 2007, Christoph Hellwig wrote:
On Thu, Mar 22, 2007 at 03:42:27PM +, Mel Gorman wrote:
A year ago, I may have agreed with you. However, Linus not only veto'd
it but
stamped on it repeatadly at VM Summit. He couldn't have made it clearer
if
he wore a t-shirt a hat
);
shp-mlock_user = current-user;
} else {
int acctflag = VM_ACCOUNT;
Otherwise, seems promising.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-static unsigned long
+unsigned long
hugetlb_get_unmapped_area(struct file *file, unsigned long addr,
unsigned long len, unsigned long pgoff, unsigned long flags)
On Fri, Mar 23, 2007 at 03:03:57PM +, Mel Gorman wrote:
What is going on here? Why do arches not get to specify
. It
might even be noticable machines with large numbers of zones if a process
started constantly reading min_free_kbytes.
This patch only calls setup_per_zone_pages_min() only on write. Tested on
an x86 laptop and it did the right thing.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
page_alloc.c
with pagetable_operations when
they really know what they are doing and why. Having the pagetable_ops
set is similar to VM_HUGETLB set as a strong sign that something unusual is
going on that is fairly easy to check for.
I prefer the additional struct to extending VMAs anyway.
--
Mel Gorman
Part-time Phd
towards the
start of memory. This is with a view of supporting memory hot-remove of
DIMMs with higher PFNs in the future. The biasing could be enforced a lot
heavier but it would cost. The last patch agressively clusters reclaimable
pages like inode caches together.
--
Mel Gorman
Part-time Phd Student
allocating
the memory is quite high.
Additional credit to Andy Whitcroft who reviewed up an earlier implementation
of the mechanism an suggested how to make it a *lot* cleaner.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
include/linux/mmzone.h | 13
include/linux/pageblock
-by: Mel Gorman [EMAIL PROTECTED]
---
fs/inode.c| 10 ++--
fs/ramfs/inode.c |1
include/asm-alpha/page.h |3 +-
include/asm-cris/page.h |3 +-
include/asm-h8300/page.h |3 +-
include/asm-i386/page.h |3 +-
include/asm-ia64/page.h |5
GFP_*_MOVABLE for one use unless people feel it would help self-documentation.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
block_dev.c |2 +-
buffer.c|2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.20-mm2
This patch adds the core of the fragmentation reduction strategy. It
works by grouping pages together based on their ability to migrate or be
reclaimed. Basically, it works by breaking the list in zone-free_area list
into MIGRATE_TYPES number of lists.
Signed-off-by: Mel Gorman [EMAIL PROTECTED
is not measurably slower for the workloads we've tested.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
page_alloc.c | 28
1 files changed, 24 insertions(+), 4 deletions(-)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.20-mm2-004_clustering_core/mm
with the standard
buddy allocator.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Signed-off-by: Joel Schopp [EMAIL PROTECTED]
---
include/linux/mmzone.h |6 ++
init/Kconfig | 13 +
mm/page_alloc.c| 31 +++
3 files changed, 50 insertions
by suspend
and hotplug.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
page_alloc.c | 28 +++-
1 files changed, 27 insertions(+), 1 deletion(-)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.20-mm2-006_configurable/mm/page_alloc.c
linux-2.6.20-mm2
-by: Mel Gorman [EMAIL PROTECTED]
---
fs/buffer.c |6 --
fs/dcache.c |2 +-
fs/ext2/super.c |3 ++-
fs/ext3/super.c |2 +-
fs/jbd/journal.c|6 --
fs/jbd/revoke.c |6
When a fallback occurs, there will be free pages for one allocation type
stored on the list for another. When a large steal occurs, this patch will
move all the free pages within one list to the other.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
page_alloc.c | 65
This patch chooses blocks with lower PFNs when placing kernel allocations. This
is particularly important during fallback in low memory situations to stop
unmovable pages being placed throughout the entire address space.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
page_alloc.c | 20
as possible by adding
a new MIGRATE_TYPE. The MIGRATE_HIGHATOMIC type are exactly what they sound
like. Care is taken that pages of other migrate types do not use the same
blocks as high-order atomic allocations.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
include/linux/mmzone.h |4 +++-
mm
agressive about stealing blocks of pages for MIGRATE_RECLAIMABLE.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
page_alloc.c | 18 +++---
1 files changed, 15 insertions(+), 3 deletions(-)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.20-mm2-011_biasplacement/mm
of problems during
review of the patches.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
to Hugh Dickens for catching issues with shmem swap
vector and ramfs allocations.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
fs/inode.c| 10 ++--
fs/ramfs/inode.c |1
include/asm-alpha/page.h |3 +-
include/asm-cris/page.h |3 +-
include/asm
-by: Mel Gorman [EMAIL PROTECTED]
---
include/linux/gfp.h|3
include/linux/mm.h |1
include/linux/mmzone.h | 19 +++
include/linux/vmstat.h |5
mm/highmem.c |7 +
mm/page_alloc.c| 229 +++-
mm/vmstat.c
external fragmentation of note as huge pages are always
the largest contiguous block we care about.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
include/linux/hugetlb.h |3 +++
include/linux/mempolicy.h |6 +++---
include/linux/sysctl.h|1 +
kernel/sysctl.c |8
This patch adds the kernelcore= parameter for x86.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
setup.c |1 +
1 files changed, 1 insertion(+)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.20-mm2-003_mark_hugepages_movable/arch/i386/kernel/setup.c
linux-2.6.20-mm2
This patch adds the kernelcore= parameter for ppc and powerpc.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
powerpc/kernel/prom.c |1 +
ppc/mm/init.c |2 ++
2 files changed, 3 insertions(+)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.20-mm2
This patch adds the kernelcore= parameter for x86_64.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
e820.c |1 +
1 files changed, 1 insertion(+)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.20-mm2-005_ppc64_set_kernelcore/arch/x86_64/kernel/e820.c
linux-2.6.20-mm2
This patch adds the kernelcore= parameter for ia64.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
efi.c |3 +++
1 files changed, 3 insertions(+)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.20-mm2-006_x8664_set_kernelcore/arch/ia64/kernel/efi.c
linux-2.6.20-mm2
Once all patches are applied, a new command-line parameter exist and a new
sysctl. This patch adds the necessary documentation.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
filesystems/proc.txt | 15 +++
kernel-parameters.txt | 16
sysctl/vm.txt
systems, I found ffplay from the ffmpeg package worked. If neither
of these work for you, the tar.gz contains the JPG files making up
the frames and you can view them with any image viewer.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
On Thu, 1 Mar 2007, Bill Irwin wrote:
On Thu, Mar 01, 2007 at 10:12:50AM +, Mel Gorman wrote:
These are figures based on kernels patches with Andy Whitcrofts reclaim
patches. You will see that the zone-based kernel is getting success rates
closer to 40% as one would expect although
On (01/03/07 16:09), Andrew Morton didst pronounce:
On Thu, 1 Mar 2007 10:12:50 +
[EMAIL PROTECTED] (Mel Gorman) wrote:
Any opinion on merging these patches into -mm
for wider testing?
I'm a little reluctant to make changes to -mm's core mm unless those
changes are reasonably
if it's simpler.
Linus
--
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
to offline is MAX_ORDER_NR_PAGES,
anti-fragmentation should group pages you can reclaim into those size of
chunks. It might simplify the number of hacks you have to perform to
limit where the kernel uses memory.
--
--
Mel Gorman
Part-time Phd Student Linux Technology
no different to today.
Linux is *not* happy on 256GB systems. Even on some 32GB systems
the swappiness setting *needs* to be tweaked before Linux will even
run in a reasonable way.
Please send testcases.
--
--
Mel Gorman
Part-time Phd Student Linux Technology
On (02/03/07 09:19), Christoph Lameter didst pronounce:
On Fri, 2 Mar 2007, Mel Gorman wrote:
However, if that is objectionable, I'd at least like to see zone-based
patches
go into -mm on the expectation that the memory hot-remove patches will be
able to use the infrastructure. It's
On Fri, 2 Mar 2007, Christoph Lameter wrote:
On Fri, 2 Mar 2007, Mel Gorman wrote:
I still think that the list based approach is sufficient for memory
hotplug if one restricts the location of the unmovable MAX_ORDER chunks
to not overlap the memory area where we would like to be able
this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
--
Mel Gorman
Part-time Phd Student Linux Technology
/sn2_defconfig .
Credit to Christoph Lameter for testing, reporting the bug and verifying
this fixes the problem. Credit to Andy Whitcroft for giving the patch a
quick review to ensure no functionality was changed.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
--
(bot:conmon-payload) disconnected
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
-by: Yasunori Goto [EMAIL PROTECTED]
Acked-by: Mel Gorman [EMAIL PROTECTED]
---
mm/page_alloc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: current_test/mm/page_alloc.c
===
--- current_test.orig/mm/page_alloc.c
On (30/12/07 12:37), Thomas Bogendoerfer didst pronounce:
On Thu, Dec 20, 2007 at 01:27:20PM +, Mel Gorman wrote:
On (20/12/07 13:43), Thomas Bogendoerfer didst pronounce:
On Thu, Dec 20, 2007 at 11:44:06AM +, Mel Gorman wrote:
--- a/include/asm-mips/page.h
+++ b/include/asm
] /a
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
-by: Mel Gorman [EMAIL PROTECTED]
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
appear to be any regressions there. The hackbench results for both
sockets and pipes were within noise.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
-
To unsubscribe from this list: send
. This
simplifies zonelist iterators in the next patch.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Christoph Lameter [EMAIL PROTECTED]
---
include/linux/swap.h |2 +-
mm/page_alloc.c |2 +-
mm/vmscan.c | 13 -
3 files changed, 10 insertions(+), 7
without problems.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
drivers/char/sysrq.c |3 +--
fs/buffer.c |6 +++---
include/linux/gfp.h | 10 +++---
include/linux/mempolicy.h |2 +-
mm/mempolicy.c|6 +++---
mm/page_alloc.c
that is allowed by the GFP flags.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Christoph Lameter [EMAIL PROTECTED]
---
arch/parisc/mm/init.c | 11 +-
fs/buffer.c|6 +
include/linux/gfp.h| 29 ---
include/linux/mmzone.h | 65 +++-
mm/hugetlb.c
for accessing the zone index
as well as the node index.
[EMAIL PROTECTED]: Suggested struct zoneref instead of embedding information in
pointers]
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Christoph Lameter [EMAIL PROTECTED]
---
arch/parisc/mm/init.c |2 -
fs/buffer.c|6
. This eliminates
the need for MPOL_BIND to create a custom zonelist. A positive benefit of
this is that allocations using MPOL_BIND now use the local-node-ordered
zonelist instead of a custom node-id-ordered zonelist.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
fs/buffer.c |2
include
nodemask is created with only the
node local to the CPU set. This allows us to eliminate the second zonelist.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
drivers/char/sysrq.c |2 -
fs/buffer.c |5 +--
include/linux/gfp.h | 23 +++
include/linux
for anything other than
emergency situations. If nothing else pools == wasted memory + a sizing
problem. But hey, it is one option.
Are we going to agree on some sort of plan or are we just going to
handwave ourselves to death?
--
Mel Gorman
Part-time Phd Student Linux
On (12/09/07 16:27), Lee Schermerhorn didst pronounce:
On Tue, 2007-09-11 at 22:30 +0100, Mel Gorman wrote:
(Sorry for the resend, I mucked up the TO: line in the earlier sending)
This is the latest version of one-zonelist and it should be solid enough
for wider testing. To briefly
On (12/09/07 14:23), Christoph Lameter didst pronounce:
On Wed, 12 Sep 2007, Mel Gorman wrote:
- z++)
- ;
+ if (likely(nodes == NULL))
+ for (; zonelist_zone_idx(z) highest_zoneidx;
+ z
: -1.02% to 1.56%
The TBench figures were too variable between runs to draw conclusions from but
there didn't appear to be any regressions there. The hackbench results for both
sockets and pipes were within noise.
--
Mel Gorman
Part-time Phd Student Linux Technology
. This
simplifies zonelist iterators in the next patch.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Christoph Lameter [EMAIL PROTECTED]
---
include/linux/swap.h |2 +-
mm/page_alloc.c |2 +-
mm/vmscan.c | 19 +++
3 files changed, 13 insertions(+), 10
without problems.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
drivers/char/sysrq.c |3 +--
fs/buffer.c |6 +++---
include/linux/gfp.h | 22 +++---
include/linux/mempolicy.h |2 +-
mm/mempolicy.c|6 +++---
mm/page_alloc.c
that is allowed by the GFP flags.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Christoph Lameter [EMAIL PROTECTED]
---
arch/parisc/mm/init.c | 11 +-
fs/buffer.c|6 +
include/linux/gfp.h| 17 +---
include/linux/mmzone.h | 65 +++-
mm/hugetlb.c
for accessing the zone index
as well as the node index.
[EMAIL PROTECTED]: Suggested struct zoneref instead of embedding information in
pointers]
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
Acked-by: Christoph Lameter [EMAIL PROTECTED]
---
arch/parisc/mm/init.c |2 -
fs/buffer.c|6
. This eliminates
the need for MPOL_BIND to create a custom zonelist. A positive benefit of
this is that allocations using MPOL_BIND now use the local-node-ordered
zonelist instead of a custom node-id-ordered zonelist.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
fs/buffer.c |2
include
nodemask is created with only the
node local to the CPU set. This allows us to eliminate the second zonelist.
Signed-off-by: Mel Gorman [EMAIL PROTECTED]
---
drivers/char/sysrq.c |2 -
fs/buffer.c |5 +--
include/linux/gfp.h | 23 +++
include/linux
1 - 100 of 10256 matches
Mail list logo
