Hi, while trying to compile 2.6.23-rc6-mm1 I came across the following build error: mgd@seneca:/usr/src/linux-2.6.23-rc6-mm1> make modules CHK include/linux/version.h CHK include/linux/utsrelease.h CALL scripts/checksyscalls.sh <stdin>:1389:2: warning: #warning syscall revokeat not implemented <stdin>:1393:2: warning: #warning syscall frevoke not implemented CC [M] drivers/acpi/sbs.o drivers/acpi/sbs.c: In function =E2=80=98acpi_battery_alarm_show=E2=80=99: ...

This adds a new gfp flag __GFP_VFALLBACK If specified during a higher order allocation then the system will fall back to vmap and attempt to create a virtually contiguous area instead of a physically contiguous area. In many cases the virtually contiguous area can stand in for the physically contiguous area (with some loss of performance). The pages used for VFALLBACK are marked with a new flag PageVcompound(page). The mark is necessary since we have to know upon free if we have to destroy a ...

Virtual fallbacks are rare and thus subtle bugs may creep in if we do not test the fallbacks. CONFIG_VFALLBACK_ALWAYS makes all GFP_VFALLBACK allocations fall back to virtual mapping. Signed-off-by: Christoph Lameter <clameter@sgi.com> --- lib/Kconfig.debug | 11 +++++++++++ mm/page_alloc.c | 9 +++++++++ 2 files changed, 20 insertions(+) Index: linux-2.6/mm/page_alloc.c =================================================================== --- linux-2.6.orig/mm/page_alloc.c 2007-...

SLAB_VFALLBACK can be specified for selected slab caches. If fallback is available then the conservative settings for higher order allocations are overridden. We then request an order that can accomodate at mininum 100 objects. The size of an individual slab allocation is allowed to reach up to 256k (order 6 on i386, order 4 on IA64). Implementing fallback requires special handling of virtual mappings in the free path. However, the impact is minimal since we already check the address if its NULL or...

This is in particular useful for large I/Os because it will allow > 100 allocs from the SLUB fast path without having to go to the page allocator. Signed-off-by: Christoph Lameter <clameter@sgi.com> --- fs/buffer.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Index: linux-2.6/fs/buffer.c =================================================================== --- linux-2.6.orig/fs/buffer.c 2007-09-18 15:44:37.000000000 -0700 +++ linux-2.6/fs/buffer.c 2007-09-18 15:44:51.000...

In an interrupt context we cannot wait for the vmlist_lock in __get_vm_area_node(). So use a trylock instead. If the trylock fails then the atomic allocation will fail and subsequently be retried. This only works because the flush_cache_vunmap in use for allocation is never performing any IPIs in contrast to flush_tlb_... in use for freeing. Signed-off-by: Christoph Lameter <clameter@sgi.com> --- mm/vmalloc.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) Index: ...

These things will clash drastically with my lazy TLB flushing and scalability work. Actually the lazy TLB flushing will provide a natural way to defer unmapping at interrupt time, and the scalability work should make it -

Avoid expensive lookups of virtual addresses from page structs by storing the vmalloc address in page->private. We can then avoid the vmalloc_address() in the get_xxxx_pagexxxx() functions and simply return page->private. Signed-off-by: Christoph Lameter <clameter@sgi.com> --- mm/page_alloc.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) Index: linux-2.6/mm/page_alloc.c =================================================================== --- linux-2.6.o...

Make vmalloc functions work the same way as kfree() and friends that take a const void * argument. Signed-off-by: Christoph Lameter <clameter@sgi.com> --- include/linux/vmalloc.h | 10 +++++----- mm/vmalloc.c | 16 ++++++++-------- 2 files changed, 13 insertions(+), 13 deletions(-) Index: linux-2.6/mm/vmalloc.c =================================================================== --- linux-2.6.orig/mm/vmalloc.c 2007-09-18 18:34:06.000000000 -0700 +++ linux-2.6/mm/vmalloc....

Currently there is a strong tendency to avoid larger page allocations in the kernel because of past fragmentation issues and the current defragmentation methods are still evolving. It is not clear to what extend they can provide reliable allocations for higher order pages (plus the definition of "reliable" seems to be in the eye of the beholder). Currently we use vmalloc allocations in many locations to provide a safe way to allocate larger arrays. That is due to the danger of higher order allocati...

cache_nice_tries and flags entry do not appear in proc fs sched_domain directory, because ctl_table entry is skipped. This patch fix the issue. Signed-off-by: Zou Nan hai <nanhai.zou@intel.com> --- linux-2.6.23-rc6/kernel/sched.c 2007-09-18 23:47:07.000000000 -0400 +++ b/kernel/sched.c 2007-09-18 23:47:20.000000000 -0400 @@ -5304,7 +5304,7 @@ set_table_entry(struct ctl_table *entry, static struct ctl_table * sd_alloc_ctl_domain_table(struct sched_domain *sd) { - struct ctl_table *ta...

This patch add a field of 64-bit physical pointer to NULL terminated single linked list of struct setup_data to real-mode kernel header. This is used as a more extensible boot parameters passing mechanism. This patch has been tested against 2.6.23-rc6-mm1 kernel on x86_64. It is based on the proposal of Peter Anvin. Known Issues: 1. Where is safe to place the linked list of setup_data? Because the length of the linked list of setup_data is variable, it can not be copied into BSS segment of ...

Sorry... I sent old version...it returns -ENOSYS. Andrew-san, please replace. Goto-san, please confirm and ack. == Now, arch dependent code around CONFIG_MEMORY_HOTREMOVE is a mess. This patch cleans up them. - For !CONFIG_MEMORY_HOTREMOVE, add generic no-op remove_memory(), which returns -EINVAL. - removed remove_pages() only used in powerpc. - removed no-op remove_memory() in i386, sh, sparc64, x86_64. - only powerpc returns -ENOSYS at memory hot remove. changes it to return -EI...

These two patches fix UML build breakages on x86_64. They are -mm-specific, so don't need to go to mainline until 2.6.24. Jeff -- Work email - jdike at linux dot intel dot com -

from: Andreas Dilger <adilger@clusterfs.com> In pass1 of e2fsck, every inode table in the fileystem is scanned and checked, regardless of whether it is in use. This is this the most time consuming part of the filesystem check. The unintialized block group feature can greatly reduce e2fsck time by eliminating checking of uninitialized inodes. With this feature, there is a a high water mark of used inodes for each block group. Block and inode bitmaps can be uninitialized on disk via a...

That's rather sad. A plain old "depends on" would be better. -

This patch fixes a crash caused by an interrupt coming in when an IRQ stack is being torn down. When this happens, handle_signal will loop, setting up the IRQ stack again because the tearing down had finished, and handling whatever signals had come in. However, to_irq_stack returns a mask of pending signals to be handled, plus bit zero is set if the IRQ stack was already active, and thus shouldn't be torn down. This causes a problem because when handle_signal goes around the loop, sig will be zer...

Run any program that opens the ALSA sound (and probably the dsp legacy), and then suspend to disk during playback. On the next and each subsequent thawout, the sound is dead even if you close and repoen the sound. Only a "cold boot" can fix it. -

Hi Balbir, I get following panic from SLUB, while doing simple fsx tests. I haven't used any container/memory controller stuff except that I configured them in :( Looks like slub doesn't like one of the flags passed in ? Known issue ? Ideas ? Thanks, Badari CONFIG_CONTAINERS=y CONFIG_CONTAINER_DEBUG=y CONFIG_CONTAINER_NS=y CONFIG_CONTAINER_CPUACCT=y CONFIG_CONTAINER_MEM_CONT=y CONFIG_ACPI_CONTAINER=m elm3b29 login: ------------[ cut here ]------------ kernel BUG at mm/slub.c:10...

Hi, Badari, The fix looks correct, radix_tree_preload() does the same thing in add_to_page_cache(). Thanks for identifying the fix -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL -

Use the mutual exclusion provided by the text edit lock in the kprobes code. It allows coherent manipulation of the kernel code by other subsystems. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> Acked-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com> CC: prasanna@in.ibm.com CC: ananth@in.ibm.com CC: anil.s.keshavamurthy@intel.com CC: davem@davemloft.net --- kernel/kprobes.c | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) Index: linu...

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> --- Documentation/immediate.txt | 228 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 228 insertions(+) Index: linux-2.6-lttng/Documentation/immediate.txt =================================================================== --- /dev/null 1970-01-01 00:00:00.000000000 +0000 +++ linux-2.6-lttng/Documentation/immediate.txt 2007-09-18 09:12:01.000000000 -0400 @@ -0,0 +1,228 @@ + Using the Immediate Values +...

Hi, Is there a standard way for drivers (RAID) to detect if the current kernel is running in kdump mode? We would like to adjust driver behavior dynamically when kdump is active by scaling down resources. Thanks -Atul Mukker LSI Corp. -

With the increasing complexity of today's user-space application and the wide deployment of SMP systems, the users need an increasing understanding of the behavior and performance of a system across multiple processes/different execution contexts/multiple CPUs. In applications such as large clusters (Google, IBM), video acquisition (Autodesk), embedded real-time systems (Wind River, Monta Vista, Sony) or sysadmin/programmer-type tasks (SystemTAP from Redhat), a tool that permits tracing of kernel-use...

Hi Andrew, Here are the updated Linux Kernel Markers. It depends on : Text Edit Lock Immediate Values Sorted module list Merge Kconfig instrumentation menu It applies to 2.6.23-rc4-mm1, in this order: linux-kernel-markers-architecture-independent-code.patch linux-kernel-markers-instrumentation-menu.patch linux-kernel-markers-documentation.patch linux-kernel-markers-port-blktrace-to-markers.patch You can find a tarball of this patch and all its dependencies at: [ message continues ]