From: Solofo Ramangalahy <Solofo.Ramangalahy@bull.net> Add /proc/sys/kernel/auto_msgmnb to control automatic recomputation of /proc/sys/kernel/msgmnb (msg_ctlmnb). Signed-off-by: Solofo Ramangalahy <Solofo.Ramangalahy@bull.net> --- Documentation/sysctl/kernel.txt | 35 ++++++++++++++++ include/linux/ipc_namespace.h | 5 ++ ipc/ipc_sysctl.c | 87 ++++++++++++++++++++++++++++++++++++---- ipc/ipcns_notifier.c | 62 +++++++++++++++++++++++++++- ipc/...

From: Solofo Ramangalahy <Solofo.Ramangalahy@bull.net> As msgmnb is scaled wrt. online cpus, cpu hotplug events should grow and shrink the value. Like msgmni with ipc_memory_callback(), the ipc_cpu_callback() function triggers msgmnb recomputation. Signed-off-by: Solofo Ramangalahy <Solofo.Ramangalahy@bull.net> --- include/linux/ipc_namespace.h | 1 + ipc/ipcns_notifier.c | 8 +++----- ipc/util.c | 28 ++++++++++++++++++++++++++++ 3 files ch...

Background: Some IBM POWER-based systems have the ability to run in a "compatibility" mode which mostly appears to the OS as a different processor from the actual hardware. This feature of the platform is useful for live partition migration and for backwards compatibility with old kernels on new hardware. For example, a Power6 system may appear to be a Power5+, which makes the AT_PLATFORM value "power5+". Problem: Booting a system in a compatibility mode means that ld.so may load libraries that...

Some IBM POWER-based platforms have the ability to run in a mode which mostly appears to the OS as a different processor from the actual hardware. For example, a Power6 system may appear to be a Power5+, which makes the AT_PLATFORM value "power5+". This means that programs are restricted to the ISA supported by Power5+; Power6-specific instructions are treated as illegal. However, some applications (virtual machines, optimized libraries) can benefit from knowledge of the underlying CPU model. A ...

Hi Greg, I wonder if you would consider this patch for sysfs. It makes sysfs_notify functionality more useful to me. Thanks, NeilBrown Author: NeilBrown <neilb@suse.de> Date: Wed Jul 16 08:54:36 2008 +1000 Support sysfs_notify from atomic context with new sysfs_notify_dirent sysfs_notify currently takes sysfs_mutex. This means that it cannot be called in atomic context. sysfs_mutex is sometimes held over a malloc (sysfs_rename_dir) so it can blo...

Linus, Please pull the latest "4096 CPUs" git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git cpus4096 this includes performance and stack footprint optimizations for crazy SGI systems with 4096 CPUs. The tree-wide scope is relatively large because automatic conversion to the faster for_each_cpu_*_nr() APIs was not possible, it had to be done one by one in the case where it was safe to iterate to nr_cpu_ids. Thanks, Ingo ------------------> A...

Add rcu_read_lock_sched() and rcu_read_unlock_sched() to rcupdate.h to match the recently added write-side call_rcu_sched() and rcu_barrier_sched(). They also match the no-so-recently-added synchronize_sched(). It will help following matching use of the update/read lock primitives. Those new read lock will replace preempt_disable()/enable() used in pair with RCU-classic synchronization. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> CC: Peter Zijlstra <peterz@infradead.o...

Instrument addr_add and del of network interfaces. Lets a tracer know the interface address changes. Those tracepoints are used by LTTng. About the performance impact of tracepoints (which is comparable to markers), even without immediate values optimizations, tests done by Hideo Aoki on ia64 show no regression. His test case was using hackbench on a kernel where scheduler instrumentation (about 5 events in code scheduler code) was added. See the "Tracepoints" patch header for performance result ...

Keep track of interface up/down for ipv4. Allows to keep track of interface address changes in a trace. Those tracepoints are used by LTTng. About the performance impact of tracepoints (which is comparable to markers), even without immediate values optimizations, tests done by Hideo Aoki on ia64 show no regression. His test case was using hackbench on a kernel where scheduler instrumentation (about 5 events in code scheduler code) was added. See the "Tracepoints" patch header for performance resu...

Implementation of kernel tracepoints. Inspired from the Linux Kernel Markers. Allows complete typing verification by declaring both tracing statement inline functions and probe registration/unregistration static inline functions within the same macro "DEFINE_TRACE". No format string is required. See the tracepoint Documentation and Samples patches for usage examples. Taken from the documentation patch : "A tracepoint placed in code provides a hook to call a function (probe) that you can provide a...

Paging activity instrumentation. Instruments page allocation/free to keep track of page allocation. This does not cover hugetlb activity, which is covered by a separate patch. Those tracepoints are used by LTTng. About the performance impact of tracepoints (which is comparable to markers), even without immediate values optimizations, tests done by Hideo Aoki on ia64 show no regression. His test case was using hackbench on a kernel where scheduler instrumentation (about 5 events in code scheduler ...

Instrumentation of hugetlb activity (alloc/free/reserve/grab/release). Those tracepoints are used by LTTng. About the performance impact of tracepoints (which is comparable to markers), even without immediate values optimizations, tests done by Hideo Aoki on ia64 show no regression. His test case was using hackbench on a kernel where scheduler instrumentation (about 5 events in code scheduler code) was added. See the "Tracepoints" patch header for performance result detail. Changelog : - instr...

Instrument the scheduler activity (sched_switch, migration, wakeups, wait for a task, signal delivery) and process/thread creation/destruction (fork, exit, kthread stop). Actually, kthread creation is not instrumented in this patch because it is architecture dependent. It allows to connect tracers such as ftrace which detects scheduling latencies, good/bad scheduler decisions. Tools like LTTng can export this scheduler information along with instrumentation of the rest of the kernel activity to perfor...

Instrumentation of IRQ related events : irq, softirq, tasklet entry and exit and softirq "raise" events. It allows tracers to perform latency analysis on those various types of interrupts and to detect interrupts with max/min/avg duration. It helps detecting driver or hardware problems which cause an ISR to take ages to execute. It has been shown to be the case with bogus hardware causing an mmio read to take a few milliseconds. Those tracepoints are used by LTTng. About the performance impact...

Hi, Here is the newest release of the Tracepoints, following the feedback from Peter Zijlstra. The main change is the creation of include/trace/ as a placeholder from tracepoint headers. The patchset applies over linux-next patch-v2.6.26-next-20080715 in this order : #This a separate RCU update upon which the tracepoints depend rcu-read-sched.patch tracepoints.patch tracepoints-documentation.patch tracepoints-samples.patch lttng-instrumentation-irq.patch lttng-instrumentation-scheduler....

-convert sunrpc debug facility Signed-off-by: Jason Baron <jbaron@redhat.com> --- fs/lockd/clntlock.c | 1 + fs/lockd/clntproc.c | 1 + fs/lockd/host.c | 1 + fs/lockd/mon.c | 1 + fs/lockd/svc.c | 1 + fs/lockd/svc4proc.c | 1 + fs/lockd/svclock.c | 1 + fs/lockd/svcproc.c | 1 + fs/lockd/svcshare.c ...

On Tue, 15 Jul 2008 18:30:03 -0400 It's on linux-kernel. If you don't have a linux-kernel subscription then you should fix that. Set up a procmail rule and do a search-by-subject when needed. In this case, yes, it would have been nice if Jason had cc'ed lots of different lists and individuals on the core patch and then selectively cc'ed lists and individuals on the per-subsystem followup patches. But I doubt if even 2% of patch submitters manage to do all that correctly. --

OK. Having looked up the missing patch on gmane, I'd like to know whether or not there is a followup plan to fix up utilities like 'rpcdebug'? Apparently this patch doesn't remove the existing sunrpc sysctl interface, but does circumvent it. The result is that while rpcdebug will happily continue to run, it just won't work any more... Trond --

Since rpcdebug + the sysctl interface are well established interfaces that are probably scripted all over the place by administrators who are using it to as a debugging tool, I'd say that any interface breakages need a managed transition period. IOW: I'd say that any changes are going to need a transition period where a compatibility mode can be compiled in and where both interfaces work. It doesn't have to be too sophisticated, perhaps just something along the lines of +# define ifdebug(fac)...

-convert aio dprintk -> pr_debug Signed-off-by: Jason Baron <jbaron@redhat.com> --- fs/aio.c | 34 ++++++++++++++-------------------- 1 files changed, 14 insertions(+), 20 deletions(-) diff --git a/fs/aio.c b/fs/aio.c index 2283686..b6f3b33 100644 --- a/fs/aio.c +++ b/fs/aio.c @@ -36,12 +36,6 @@ #include <asm/uaccess.h> #include <asm/mmu_context.h> -#if DEBUG > 1 -#define dprintk printk -#else -#define dprintk(x...) do { ; } while (0) -#endif - /...

hi, I've updated the userspace interface and updated the implementation. I'm going to summarize what has changed below, but for more background, please see: http://marc.info/?l=linux-kernel&m=121338359012058&w=2 INTERFACE - userspace The file <debugfs>/dynamic_printk/modules is now formatted as: <module_name> <enabled=0/1> <level=[0-n]> <flag_name=0/1>.... <associated module names> . . . <module_name> : Name of the module in ...

-convert cpufreq Signed-off-by: Jason Baron <jbaron@redhat.com> --- arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c | 7 ++- arch/x86/kernel/cpu/cpufreq/cpufreq-nforce2.c | 6 ++- arch/x86/kernel/cpu/cpufreq/gx-suspmod.c | 7 ++- arch/x86/kernel/cpu/cpufreq/longhaul.c | 7 ++- arch/x86/kernel/cpu/cpufreq/longrun.c | 6 ++- arch/x86/kernel/cpu/cpufreq/p4-clockmod.c | 7 +++ arch/x86/kernel/cpu/cpufreq/powernow-k7.c | ...

-convert bonding to dynamic printk Signed-off-by: Jason Baron <jbaron@redhat.com> --- drivers/net/bonding/bonding.h | 7 +------ 1 files changed, 1 insertions(+), 6 deletions(-) diff --git a/drivers/net/bonding/bonding.h b/drivers/net/bonding/bonding.h index a3c74e2..28556dd 100644 --- a/drivers/net/bonding/bonding.h +++ b/drivers/net/bonding/bonding.h @@ -29,13 +29,8 @@ #define BOND_MAX_ARP_TARGETS 16 -#ifdef BONDING_DEBUG #define dprintk(fmt, args...) \ - printk(...

* This patch replaces the dangerous lvalue version of cpumask_of_cpu with new cpumask_of_cpu_ptr macros. These are patterned after the node_to_cpumask_ptr macros. In general terms, if there is a cpumask_of_cpu_map[] then a pointer to the cpumask_of_cpu_map[cpu] entry is used. The cpumask_of_cpu_map is provided when there is a large NR_CPUS count, reducing greatly the amount of code generated and stack space used for cpumask_of_cpu(). The pointer to the cpumask_t val...

* Patch 1 replaces the dangerous lvalue version of cpumask_of_cpu with new cpumask_of_cpu_ptr macros. These are patterned after the node_to_cpumask_ptr macros. * Patches 2..6 optimizes various places where a pointer to the cpumask_of_cpu value will result in reducing stack pressure. * Patch 7 provides a generic set of CPUMASK_ALLOC macros patterned after the SCHED_CPUMASK_ALLOC macros. This is used where multiple cpumask_t variables are declared on the stack to reduc...