An error occurred fetching the project authors.
- 25 May, 2003 40 commits
-
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> mpc_apicid is a u8, and MAX_APICS can be 256.
-
Andrew Morton authored
fs/compat.c: In function `compat_sys_ioctl': fs/compat.c:324: warning: implicit declaration of function `siocdevprivate_ioctl'
-
Andrew Morton authored
Don't assume the size of dev_t: on ppc64 it is unsignedlong and this generates a printk warning.
-
Andrew Morton authored
arch/ppc64/kernel/htab.c:105: warning: implicit declaration of function `pSeries_lpar_hpte_insert' arch/ppc64/kernel/htab.c:109: warning: implicit declaration of function `pSeries_hpte_insert'
-
Andrew Morton authored
Fix a printk warning
-
Andrew Morton authored
two printk warnings
-
Andrew Morton authored
warning: assignment makes pointer from integer without a cast
-
Andrew Morton authored
It needs sched.h for `current'.
-
Andrew Morton authored
From: David Gibson <david@gibson.dropbear.id.au> This removes a bunch of unused variables in prom_init(), squashing the associated warnings.
-
Andrew Morton authored
From: David Gibson <david@gibson.dropbear.id.au> xics.c uses ppc64_boot_msg() without prototype, this fixes it by inclding <asm/machdep.h>.
-
Andrew Morton authored
do_signal32() is used before it is defined, this prototype squashes the warning.
-
Andrew Morton authored
From: David Gibson <david@gibson.dropbear.id.au> Squash implicit declaration warning in ppc64 align.c
-
Andrew Morton authored
From: David Gibson <david@gibson.dropbear.id.au> addnote in arch/ppc64/boot (a userspace tool, not kernel code) uses exit() without including stdlib.h.
-
Andrew Morton authored
PPC64 irq return fix
-
Andrew Morton authored
Fix some warnings in the ppc64 build. Also declare a couple of AIO functions in aio.h rather than aio.c They are needed for 32-bit emulation support.
-
Andrew Morton authored
From: Anton Blanchard <anton@samba.org> PPC64 32/64-bit emulation for AIO.
-
Linus Torvalds authored
Very early initialization (core_initcall) needs to have the cdev initialization done. So make it part of the pre-initcall sequence, the same way the bdev caches were done.
-
Linus Torvalds authored
-
Ingo Molnar authored
This addresses a futex related SMP scalability problem of glibc. A number of regressions have been reported to the NTPL mailing list when going to many CPUs, for applications that use condition variables and the pthread_cond_broadcast() API call. Using this functionality, testcode shows a slowdown from 0.12 seconds runtime to over 237 seconds (!) runtime, on 4-CPU systems. pthread condition variables use two futex-backed mutex-alike locks: an internal one for the glibc CV state itself, and a user-supplied mutex which the API guarantees to take in certain codepaths. (Unfortunately the user-supplied mutex cannot be used to protect the CV state, so we've got to deal with two locks.) The cause of the slowdown is a 'swarm effect': if lots of threads are blocked on a condition variable, and pthread_cond_broadcast() is done, then glibc first does a FUTEX_WAKE on the cv-internal mutex, then down a mutex_down() on the user-supplied mutex. Ie. a swarm of threads is created which all race to serialize on the user-supplied mutex. The more threads are used, the more likely it becomes that the scheduler will balance them over to other CPUs - where they just schedule, try to lock the mutex, and go to sleep. This 'swarm effect' is purely technical, a side-effect of glibc's use of futexes, and the imperfect coupling of the two locks. the solution to this problem is to not wake up the swarm of threads, but 'requeue' them from the CV-internal mutex to the user-supplied mutex. The attached patch adds the FUTEX_REQUEUE feature FUTEX_REQUEUE requeues N threads from futex address A to futex address B. This way glibc can wake up a single thread (which will take the user-mutex), and can requeue the rest, with a single system-call. Ulrich Drepper has implemented FUTEX_REQUEUE support in glibc, and a number of people have tested it over the past couple of weeks. Here are the measurements done by Saurabh Desai: System: 4xPIII 700MHz ./cond-perf -r 100 -n 200: 1p 2p 4p Default NPTL: 0.120s 0.211s 237.407s requeue NPTL: 0.124s 0.156s 0.040s ./cond-perf -r 1000 -n 100: Default NPTL: 0.276s 0.412s 0.530s requeue NPTL: 0.349s 0.503s 0.550s ./pp -v -n 128 -i 1000 -S 32768: Default NPTL: 128 games in 1.111s 1.270s 16.894s requeue NPTL: 128 games in 1.111s 1.959s 2.426s ./pp -v -n 1024 -i 10 -S 32768: Default NPTL: 1024 games in 0.181s 0.394s incompleted 2m+ requeue NPTL: 1024 games in 0.166s 0.254s 0.341s the speedup with increasing number of threads is quite significant, in the 128 threads, case it's more than 8 times. In the cond-perf test, on 4 CPUs it's almost infinitely faster than the 'swarm of threads' catastrophy triggered by the old code.
-
Alexander Viro authored
new fields in struct inode - i_cdev and i_cindex. When we do open() on a character device we cache result of cdev lookup in inode and put the inode on a cyclic list anchored in cdev. If we already have that done, we don't bother with any lookups. When inode disappears it's removed from the list. When cdev gets unregistered we remove all cached references to it (and remove such inodes from the list). cdev is held until final fput() now.
-
Alexander Viro authored
New object: struct cdev. It contains a kobject, a pointer to file_operations and a pointer to owner module. These guys have a search structure of the same sort as gendisks and chrdev_open() picks file_operations from them. Intended use: embed such animal in driver-owned structure (e.g. tty_driver) and register it as associated with given range of device numbers. Generic code will do lookup for such object and use it for the rest. The behaviour of register_chrdev() is _not_ changed - it allocates struct cdev and registers it; any old driver will work as if nothing had changed. On that stage we only use it during chrdev_open() to find file_operations. Later it will be cached in inode->i_cdev (and index in range - in inode->i_cindex) so that ->open() could get whatever objects it wants directly without any special-cased lookups, etc.
-
Alexander Viro authored
code responsible for gendisk lookups taken out in drivers/base and generalized - now it allows to have a range-based mapping from numbers to kobjects for given struct subsystem.
-
Alexander Viro authored
register_chrdev_region() sanitized, code in tty_io.c that dealt with it cleaned up.
-
Alexander Viro authored
preparation to cdev-cidr - the lookup mechanism for gendisks is switched to dealing with disk->kobj instead of disk.
-
Alexander Viro authored
pt.c fed through Lindent
-
Alexander Viro authored
Remove cpp abuses - same as had been done for pd/pf/pcd.
-
Alexander Viro authored
Remove the rest of cpp abuse in pg.c
-
Alexander Viro authored
pg.c fed through Lindent
-
Alexander Viro authored
This removes cpp abuses - same as had been done for pd/pf/pcd.
-
Alexander Viro authored
This restores the special-case behaviour of open() on the minor 0; cpqarray allows to open that guy for ioctls even if nothing is configured. That got broken when gendisk patches went in. Patch restores the old behaviour by keeping gendisk for the first disk on controller always registered; instead of unregistering it we set size to 0.
-
Alexander Viro authored
This fixes the TIOCCONS race; it's the same as the 2.4 patch except for a fix for a brown-paperbag bug in it.
-
Geert Uytterhoeven authored
Forgot to remove include/asm-ppc/linux_logo.h when integrating the new logo code.
-
Geert Uytterhoeven authored
Atafb bug in #if 0 code (from 2.4.x)
-
Geert Uytterhoeven authored
Use new wd33c93_{abort,host_reset}() routines introduced in 2.5.67 in the m68k wd33c93-based SCSI host adapter drivers: - Amiga A2091 SCSI - Amiga A3000 SCSI - Amiga GVP Series II SCSI - MVME147 SCSI These drivers still have to implement their own adapter-specific bus_reset() routines!
-
Geert Uytterhoeven authored
Kill warning about unused static functions if HAVE_ARCH_GET_SIGNAL_TO_DELIVER is defined.
-
Geert Uytterhoeven authored
Q40/Q60 IDE: Use the standard IDE operations, which are always MMIO on m68k, but make sure IDE shows up in /proc/ioports (from Richard Zidlicky).
-
Geert Uytterhoeven authored
M68k raw I/O updates: - Convert raw I/O access macros to inline functions: o raw_{in,out}s[bw]() o raw_{in,out}sw_swapw() - Add raw_{in,out}sl() (needed for IDE) - Update isa_[im]t_[bw]() for stricter type checking of inline functions
-
Geert Uytterhoeven authored
Amifb: Updates for fbdev changes in 2.5.66 and 2.5.68: - Last parameter of fb_{fillrect,copyarea,imageblit}() became const
-
Geert Uytterhoeven authored
IDE I/O operations clean ups: - Kill warning about void return type not being ignored - Fix comment: Q40/Q60 also has a byte-swapped IDE interface
-
Geert Uytterhoeven authored
M68k IDE: - Update for new-style low-level IDE operations. Since so far no single m68k platform uses ISA/PCI I/O space for IDE, we always use the `raw' MMIO versions. - ATA_ARCH_LOCK was renamed to IDE_ARCH_LOCK - Define ide_ack_intr() and set IDE_ARCH_ACK_INTR
-