- 09 Feb, 2002 17 commits
-
-
Jeff Garzik authored
into rum.normnet.org:/spare/vanilla/net-drivers-2.5
-
Linus Torvalds authored
update
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Dave Jones authored
Big bits first, I'll redo the smaller bits tomorrow after some sleep. Same as last time, rediffed against pre5
-
Linus Torvalds authored
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Paul Gortmaker authored
There are a couple of errors in the DMA changes to the aha1542.c driver that appeared in 2.5.4pre3: - a typo (BUF vs BUS) - a macro handed a page instead of a scatterlist - printk format length mismatch Paul.
-
Linus Torvalds authored
-
Alexander Viro authored
Make dentry and ->i_sem manipulations in driverfs explicit. Something is seriously rotten there and real fixes will take non-trivial work (e.g, I suspect that we actually ought to kill driverfs_rename() - at least cross-directory one for regular files, maybe completely). This patch simply cleans the ground.
-
Alexander Viro authored
Mostly cosmetical cleanup - sane variable names, etc. That's pretty much it for balloc.c cleanups - stuff after that will be about decent threading.
-
Alexander Viro authored
in ext2_new_block() inode->i_sb can't be NULL. Dead code removed. merged returns in ext2_new_block() in ext2_new_block() added a local variable (sbi) for sb->u.ext2_sb; users converted. calculation of prealloc_goal moved into beginning of function. new local variable (block). Initialized to 0, set to the number of allocated block only when we are known to be successful. ext2_new_block() returns the value of 'block' now. As the result, out: is gone - it's identical to out_unlock now. check for block being chosen past the end of disk had been moved up No sense to check that after we had done the preallocations... quota allocation taken into the beginning of ext2_new_block(). we put the number of blocks we'd reserved into dq_alloc and then decrement it each time old code would do DQUOT_ALLOC/increment when it would do DQUOT_FREE. On the exit we release dq_alloc blocks I.e. all allocations are pushed into the beginning and all freeing - to the end. now that we had moved the last possible point of failure up, we can do the same with assignment of final result to block. code that does allocation within a group had been taken out into a helper - grab_block(map, size, goal). decrementing fs-wide free blocks count moved into the beginning of function. We try to reserve up to dq_alloc blocks - amount we _can_ grab is limited by the actual free space and root-reserved percentage. That logics had been taken into a helper - reserve_blocks(sb, amount). Number of blocks we had managed to reserve is put into es_alloc. When we actually grab a block, es_alloc is decremented. Upon the exit we release the leftovers. Old code didn't honor 'reserved for root' limit when doing prealloc - now that had been fixed. EXT2_BLOCKS_PER_GROUP(sb) put into a local variable (group_size) similar "reserve and release leftovers in the end" scheme for group (i.e. we try to reserve as much as we want in the group, then count how much had been used up and release the leftovers in the end). cleaned up the preallocation loop.
-
Alexander Viro authored
minor cleanup: update 'freed' only after we finish with group
-
Alexander Viro authored
in ext2_free_blocks() inode->i_sb can't be NULL; dead code removed.
-
Alexander Viro authored
new helper - group_release_blocks(desc, bh, count); updates free blocks count for given group ext2_free_blocks now counts the blocks freed in group and updates the per-group free blocks count at once.
-
Alexander Viro authored
we postpone releasing the quota until the end of ext2_free_blocks() and do that at once.
-
Alexander Viro authored
new helper function - release_blocks(sb, n); in ext2_free_blocks() we count the blocks we'd freed and update the fs-wide count of free blocks in the end - just before unlocking superblock. instead of doing that step at a time. reviewed by ext2 folks
-
Robert Love authored
On Sat, 2002-02-09 at 01:43, Linus Torvalds wrote: > That will clean up all your issues with header file ordering. You are right, it did. I removed all the sched.h dependencies and this reduced the size of the patch greatly. I now use current_thread_info() and none of the header or include hackery from before. I've tested this with and without preemption enabled with success. I appreciate your help with this. Again, this is a minimal i386-only patch. I have other arches, documentation, etc. Patch against 2.5.4-pre5. Enjoy, Robert Love
-
- 08 Feb, 2002 23 commits
-
-
Jeff Garzik authored
to the current driver.
-
Jeff Garzik authored
Andrew Morton and Hanno Boeck. Three constants are substituted with their numeric equivalents, a reverse of the norm, to make the linear progression of PCI ids more clear, and easier to validate at a glance.
-
Alexander Viro authored
Fix lost argument to "connect()"
-
Linus Torvalds authored
-
Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Patrick Mochel authored
struct device has no ->sysdata and ->device should be ->dev
-
Alexander Viro authored
exp_procfs_exports() switched to seq_..., missing lock added.
-
Alexander Viro authored
all exports for given client are put on the cyclic list (->cl_list/->ex_list). Code cleaned up.
-
Alexander Viro authored
exports hash switched to use of struct list_head, code cleaned up.
-
Dave Jones authored
Change to use the new include/linux/zconf.h
-
Dave Jones authored
Additional descriptions that got lost along the way somewhere. Also updates some extra IDE options that shared the same fate.
-
Dave Jones authored
unneeded these days..
-
Dave Jones authored
- Reorder mainmenu items so CONFIG_EXPERIMENTAL is at the top again. - Various updates from 2.4
-
Dave Jones authored
-
Dave Jones authored
2.4/2.5 kernels suffer from an infinitely long hang when a serial tty device is closed, and there are characters waiting to be sent. The hang occurs in tty_wait_until_sent. There is a timeout 'closing_wait' which defines how long to wait for the TX buffers to empty; the problem is that the serial layer totally ignores it. It is stored in two structures, 'info' and 'state'. It is initialised in the 'state' structure, but used from the 'info' structure. It turns out that 'hub6' was also missing. I'm not currently clear what the expected behaviour should be when the timeout is changed via setserial, and others have the port open - I've opted to preserve the timeout until all users close the port. It's trivial to change this behaviour though.
-
Dave Jones authored
Mostly from 2.4.17 / 18pre. - Code cleanup - Fix suspend/resume on several chipsets - Add support for i820.
-
Dave Jones authored
Make spinlocks etc use subsections of their parent sections instead of an ELF section of their own - needed for newer binutils when the parent sector is removed.
-
Dave Jones authored
Newer Athlons have means of checking if they are SMP capable or not. This code adds checks that printk a warning on systems not intended for SMP, and set the taint flag that modutils is already aware of. The taint code is also improved to use defines instead of magic numbers.
-
http://linuxusb.bkbits.net/linus-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Greg Kroah-Hartman authored
-
http://gkernel.bkbits.net/vm-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Jeff Garzik authored
swap_info_struct became pretty much superfluous. As we are minimizing kdev_t usage anyway, I took the opportunity to remove swap_device member, and replace the remaining usages with SWP_BLOCKDEV bit flag. Adding SWP_BLOCKDEV in turn motivated a small cleanup of the SWP_xxx bit flags and their usage. Patch has been in light testing for a couple weeks, and has been glanced at by Al. "looks sane"
-