history/include/linux, branch master

[PATCH] ext3: move goal logical block into block allocation info structure

2005-04-04T00:39:47Z

Moved i_next_alloc_block and i_next_goal_block out from ext3_inod_info, and put it together with the reservation structure into the ext3_block_alloc_info structure, and dynamically allocate that structure whenever need to allocation a block. This is also apply for noreservation mount. Also cleanup ext3_find_goal() code. Signed-off-by: Mingming Cao Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] ext3: reservation info cleanup: remove rsv_seqlock

2005-04-04T00:39:31Z

Since now the ei->truncate_sem is guarding the concurrent allocation and the deallocation, there is no need to use the the rsv_seqlock lock in the ext3_reserve_window_node, which was there to protect using/allocating reservation window race between two threads allocating blocks at the same time. Signed-off-by: Mingming Cao Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] ext3: dynamic allocation of block reservation info

2005-04-04T00:39:16Z

Right now the ext3 reservation structure(ext3_reserve_window_node) is part of the ext3 inode itself. This part of information is only needed for files that need allocate blocks on disk. So, the attached patches reduce the ext3 inode size by dynamically allocating the block allocation/reservation info structure(called struct ext3_block_alloc_info) when it is needed(i.e. only for files who need to allocate blocks) The reservation structure is being allocated and linked to the ext3 inode at ext3_get_block_handle(), and being freed and unlinked at the iput_final->ext3_clear_inode(). The ei->truncate_sem which is currently used to protect concurrent ext3_get_block() and ext3_truncate is used to protect reservation structure allocation and deallocation. Signed-off-by: Mingming Cao Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] BDI: Improve nommu mmap support

2005-04-04T00:36:18Z

The attached patch improves nommu mmap support; particularly in terms on supporting private mappings. It does this by examining the device capability mask now in the backing_dev_info structure. Private mappings will now be backed by the underlying device directly if possible, where "possible" is constrained by the protection mask parameter and the device capabilities mask. I've also split the do_mmap_pgoff() function contents into a number of auxilliary functions to make it easier to understand. The documentation is also updated; including the addition of a warning about permitting direct mapping of flash chips and the problems of XIP vs write. Signed-Off-By: David Howells Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

Merge bk://bart.bkbits.net/ide-2.6

2005-04-03T13:02:24Z

into ppc970.osdl.org:/home/torvalds/v2.6/linux

[ide] kill ide_drive_t->disk

2005-04-02T17:49:01Z

* move ->disk from ide_drive_t to driver specific objects * make drivers allocate struct gendisk and setup rq->rq_disk (there is no need to do this for REQ_DRIVE_TASKFILE requests) * add ide_init_disk() helper and kill alloc_disks() in ide-probe.c * kill no longer needed ide_open() and ide_fops[] in ide.c ide_init_disk() fixed by Andrew Morton . Signed-off-by: Bartlomiej Zolnierkiewicz

[ide] add ide_{un}register_region()

2005-04-02T17:38:19Z

Add ide_{un}register_region() and fix ide-{tape,scsi}.c to register block device number ranges. In ata_probe() only probe for modules. Behavior is unchanged because: * if driver is already loaded and attached to drive ata_probe() is not called et all * if driver is loaded by ata_probe() it will register new number range for a drive and this range will be found by kobj_lookup() If this is not clear please read http://lwn.net/Articles/25711/ and see drivers/base/map.c. This patch makes it possible to move drive->disk allocation from ide-probe.c to device drivers. Signed-off-by: Bartlomiej Zolnierkiewicz

Merge bk://kernel.bkbits.net/gregkh/linux/pci-2.6

2005-04-01T14:04:53Z

into ppc970.osdl.org:/home/torvalds/v2.6/linux

merge

2005-04-01T04:36:30Z

[PATCH] I2C: Move functionality handling from i2c-core to i2c.h

2005-04-01T03:49:04Z

So far, the functionality handling of i2c adapters was done in i2c-core by two exported functions: i2c_get_functionality and i2c_check_functionality. I found that both functions could be reduced to one line each, and propose that we turn them into inline function in the i2c.h header file, much like other i2c helper functions (e.g. i2c_get_clientdata, i2c_set_clientdata and i2c_clientname). The conversion of i2c_get_functionality suppresses a legacy check which shouldn't be needed anymore. Only one driver (s3c2410) was still relying on it, and was fixed some days ago. The conversion lets us get rid of two exports. Not only i2c-core gets smaller (by 458 bytes), but the client drivers using these functions get smaller too (typically by 48 bytes). And of course the new way is likely to be faster too, even if it wasn't my primary objective. Signed-off-by: Jean Delvare Signed-off-by: Greg Kroah-Hartman