This cleans up the formatting in the vDSO linker script, mostly just the use of whitespace. It's intended to approximate the kernel standard conventions for indenting C, treating elements of the linker script about like initialized variable definitions. Signed-off-by: Roland McGrath <roland@redhat.com> CC: Sam Ravnborg <sam@ravnborg.org> --- arch/powerpc/kernel/vdso32/vdso32.lds.S | 219 +++++++++++++++++-------------- 1 files changed, 118 insertions(+), 101 deletions(-) diff -...

This cleans up the formatting in the vDSO linker script, mostly just the use of whitespace. It's intended to approximate the kernel standard conventions for indenting C, treating elements of the linker script about like initialized variable definitions. Signed-off-by: Roland McGrath <roland@redhat.com> CC: Sam Ravnborg <sam@ravnborg.org> --- arch/sh/kernel/vsyscall/vsyscall.lds.S | 77 +++++++++++++++++-------------- 1 files changed, 42 insertions(+), 35 deletions(-) diff --gi...

I am not subscribed to LKML, so please CC me in replies. I am reporting a regression when CONFIG_DEBUG_LOCKDEP is enabled in 2.6.23-git8. The error occurs immediately before loading init. Complete dmesg and kernel config are attached. [ 28.528074] VFS: Mounted root (ext3 filesystem) readonly. [ 28.528090] Freeing unused kernel memory: 212k freed [ 28.537431] Write protecting the kernel read-only data: 1036k [ 28.622874] WARNING: at kernel/lockdep.c:2658 check_flags() [ 28.625132] [ 28...

From 7dd503c612afcb86b3165602ab264e2e9493b4bf Mon Sep 17 00:00:00 2001 From: Serge E. Hallyn <serue@us.ibm.com> Date: Mon, 15 Oct 2007 20:57:52 -0400 Subject: [RFC] [PATCH 2/2] capabilities: implement 64-bit capabilities We are out of capabilities in the 32-bit capability fields, and several users could make use of additional capabilities. Convert the capabilities to 64-bits, change the capability version number accordingly, and convert the file capability code to handle both 32-bit and 64-b...

This patch accomplishes the following goals: * kill the 'pci_enable_device ret val not checked' warning * eliminate the incorrect mucking with pci_dev::current_state via the following changes: * [minor bug fix] eliminate pci_set_power_state() call in resume, pci_enable_device() does so for us. * [bug fix] do not touch dev->current_state, pci_set_power_state() and other PCI layer functions manage this for us. * [minor bug fix, warning fix] check pci_enable_device() ret val in re...

From: Randy Dunlap <randy.dunlap@oracle.com> Fix filesystems docbook warnings. Warning(linux-2.6.23-git8//fs/debugfs/file.c:241): No description found for parameter 'name' Warning(linux-2.6.23-git8//fs/debugfs/file.c:241): No description found for parameter 'mode' Warning(linux-2.6.23-git8//fs/debugfs/file.c:241): No description found for parameter 'parent' Warning(linux-2.6.23-git8//fs/debugfs/file.c:241): No description found for parameter 'value' Warning(linux-2.6.23-git8//include/linux/j...

From: Randy Dunlap <randy.dunlap@oracle.com> Fix kernel-api docbook warnings. Warning(linux-2.6.23-git8//drivers/message/fusion/mptscsih.c:2618): No description found for parameter 'sc' Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> --- drivers/message/fusion/mptscsih.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) --- linux-2.6.23-git8.orig/drivers/message/fusion/mptscsih.c +++ linux-2.6.23-git8/drivers/message/fusion/mptscsih.c @@ -2605,14 +2605,10...

Apples to oranges, Chris ;) btrfs linearises writes due to it's COW behaviour and this is trades off read speed. i.e. we take more seeks to read data so we can keep the write speed high. By using large blocks, you're reducing the number of seeks needed to find anything, and hence the read speed will increase. Write speed will be pretty much unchanged because btrfs does linear writes no matter the block size. XFS doesn't linearise writes and optimises it's layout for a large number of disks and...

It isn't that hard to add simple kset attributes, so don't go through all the gyrations of creating your own object type and show and store functions. Just use the functions that are already present. This makes things much simpler. Note, the version_str string violates the "one value per file" rule for sysfs. I suggest changing this now (individual files per type supported is one suggested way.) Cc: Michael A. Halcrow <mahalcro@us.ibm.com> Cc: Michael C. Thompson <mcthomps@us.ibm.c...

> There is a /proc/sys/net/ipv4/ip_dynaddr sysctl in 2.6.21. Actually, it does look promising, thanks. Stefan -

No, but it dramatically reduces that value of being able to enumerate Breaking old behaviour is always bad... My computers with IDE interfaces still see stable "/dev/hda" devices. Are you saying the devices that used to be "hda" are now "sdb" ?? Maybe there is a Depends on your metric. "Easy to type" - I guess /dev/hda1 wins hands down. "Can be used in a script or config file and is guaranteed always to work until a screwdriver is used to change that device or it's controller" I think...

Hi. I've noticed that with recent kernels (starting somewhere between 2.6.20 and 2.6.22) I sometimes get *lots* of disk activity on resume from suspend to ram. About 2/3 of the time, the system resumes normally but in the remaining 1/3 of the time, the hard drive light stays on almost solid and the machine is very, very slow to respond. The only way I've found to reliably recover from this is if I can get to a command prompt fast enough and do "shutdown -r now". There's not much cpu activity at ...

Yup, they slipped through. I have fixups in my pile already. Will send them tomorrow when I'm actually awake. tglx -

This patchset is version 3 of my /proc/pid/pagemaps code. Rather than submit about 30 incremental patches atop an existing 20 or so where many of the intermediate states are broken and get undone anyway, I've respun this as a much smaller set of 11 patches. Changes in this series: - headers gone again (as recommended by Dave Hansen and Alan Cox) - 64-bit entries (as per discussion with Andi Kleen) - swap pte information exported (from Dave Hansen) - page walker callback for holes (from Dave Ha...

How about pulling the EMBEDDED off there? I certainly want it for non-embedded reasons. ;) -- Dave -

But it's at the least confusing. Surely this option should depend on MMU and PROC_FS, and the prompt depend on EMBEDDED? That might be implied by the Kconfig layout, but AFAICT this patch removed the explicit MMU dependency. Rusty. -

From: Matt Mackall <mpm@selenic.com> This makes physical page map counts available to userspace. Together with /proc/pid/pagemap and /proc/pid/clear_refs, this can be used to monitor memory usage on a per-page basis. [bunk@stusta.de: make struct proc_kpagemap static] Signed-off-by: Matt Mackall <mpm@selenic.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: David Rientjes <rientjes@google.com> Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Andrew Morton...

Hmm, I would have thought you'd find the NUMA bits especially interesting. Being able to, say, colorize a process' memory map by what nodes its That is a concern. In general, I think getting too cute with page flags and struct page in general is a bad idea because the rules here are already so complex/fragile/confusing/underdocumented, but there's Referenced, dirty, uptodate, lru, active, slab, writeback, reclaim, and buddy all look like they might be interesting to me from the point of view of...

Yeah, there are a bunch of flags that aren't mutually exclusive and we Perhaps we need something like: flags = page->flags; userflags = FLAG_BIT(USER_REFERENCED, flags & PG_referenced) | ... etc. for the flags we want to export. This will let us change to FLAG_BIT(USER_SLAB, PageSlab(page)) | if we make a virtual slab bit. And it shows up in grep. Unfortunately, i386 test_bit is an asm inline and not a macro so we can't hope for the compiler to fold up a bunch of i...

Perhaps. SLUB is still "a slab-based allocator". SLOB isn't, but I Confused. Why are we interested in clear? -- Mathematics is the supreme nostalgia of our time. -

For the /proc/<pid>/pagemap code[1], we need to able to query how much virtual address space a particular task has. The trick is that we do it through /proc and can't use TASK_SIZE since it references "current" on some arches. The process opening the /proc file might be a 32-bit process opening a 64-bit process's pagemap file. x86_64 already has a TASK_SIZE_OF() macro: #define TASK_SIZE_OF(child) ((test_tsk_thread_flag(child, TIF_IA32)) ? IA32_PAGE_OFFSET : TASK_SIZE64) I'd like to...

David, All of your comments looked pretty valid to me. I've refreshed that patch. I haven't even compile-tested this so there may be some fat fingering somewhere. I'll run compile tests on it now. -- Dave For the /proc/<pid>/pagemap code[1], we need to able to query how much virtual address space a particular task has. The trick is that we do it through /proc and can't use TASK_SIZE since it references "current" on some arches. The process opening the /proc file might be a 32-b...

From: Matt Mackall <mpm@selenic.com> Reorder source so that all the code and data for each interface is together. Signed-off-by: Matt Mackall <mpm@selenic.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: David Rientjes <rientjes@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Index: l/fs/proc/task_mmu.c =================================================================== --- l.orig/fs/proc/task_mmu.c 2007-10-14 13:42:11.000000000 -0500 +++ l...

From: Matt Mackall <mpm@selenic.com> This puts all the clear_refs code where it belongs and probably lets things compile on MMU-less systems as well. Signed-off-by: Matt Mackall <mpm@selenic.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: David Rientjes <rientjes@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Index: l/fs/proc/base.c =================================================================== --- l.orig/fs/proc/base.c 2007-10-14 13...

It would be nice to have some clue about when each of these functions are called (depth first? pre or post order?), and what their params are. Does it call a callback for folded pagetable levels? Can pte_hole be used to create new mappings while we're traversing the Should this be (pte, addr, addr+PAGE_SIZE, private)? Is the second addr argument for the address range being mapped by this thing? Why pass -