Loading CREDITS +9 −0 Original line number Diff line number Diff line Loading @@ -495,6 +495,11 @@ S: Kopmansg 2 S: 411 13 Goteborg S: Sweden N: Paul Bristow E: paul@paulbristow.net W: http://paulbristow.net/linux/idefloppy.html D: Maintainer of IDE/ATAPI floppy driver N: Dominik Brodowski E: linux@brodo.de W: http://www.brodo.de/ Loading Loading @@ -2642,6 +2647,10 @@ S: C/ Mieses 20, 9-B S: Valladolid 47009 S: Spain N: Gadi Oxman E: gadio@netvision.net.il D: Original author and maintainer of IDE/ATAPI floppy/tape drivers N: Greg Page E: gpage@sovereign.org D: IPX development and support Loading Documentation/ABI/testing/sysfs-bus-pci +70 −0 Original line number Diff line number Diff line Loading @@ -41,6 +41,49 @@ Description: for the device and attempt to bind to it. For example: # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id What: /sys/bus/pci/drivers/.../remove_id Date: February 2009 Contact: Chris Wright <chrisw@sous-sol.org> Description: Writing a device ID to this file will remove an ID that was dynamically added via the new_id sysfs entry. The format for the device ID is: VVVV DDDD SVVV SDDD CCCC MMMM. That is Vendor ID, Device ID, Subsystem Vendor ID, Subsystem Device ID, Class, and Class Mask. The Vendor ID and Device ID fields are required, the rest are optional. After successfully removing an ID, the driver will no longer support the device. This is useful to ensure auto probing won't match the driver to the device. For example: # echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id What: /sys/bus/pci/rescan Date: January 2009 Contact: Linux PCI developers <linux-pci@vger.kernel.org> Description: Writing a non-zero value to this attribute will force a rescan of all PCI buses in the system, and re-discover previously removed devices. Depends on CONFIG_HOTPLUG. What: /sys/bus/pci/devices/.../remove Date: January 2009 Contact: Linux PCI developers <linux-pci@vger.kernel.org> Description: Writing a non-zero value to this attribute will hot-remove the PCI device and any of its children. Depends on CONFIG_HOTPLUG. What: /sys/bus/pci/devices/.../rescan Date: January 2009 Contact: Linux PCI developers <linux-pci@vger.kernel.org> Description: Writing a non-zero value to this attribute will force a rescan of the device's parent bus and all child buses, and re-discover devices removed earlier from this part of the device tree. Depends on CONFIG_HOTPLUG. What: /sys/bus/pci/devices/.../vpd Date: February 2008 Contact: Ben Hutchings <bhutchings@solarflare.com> Loading @@ -52,3 +95,30 @@ Description: that some devices may have malformatted data. If the underlying VPD has a writable section then the corresponding section of this file will be writable. What: /sys/bus/pci/devices/.../virtfnN Date: March 2009 Contact: Yu Zhao <yu.zhao@intel.com> Description: This symbolic link appears when hardware supports the SR-IOV capability and the Physical Function driver has enabled it. The symbolic link points to the PCI device sysfs entry of the Virtual Function whose index is N (0...MaxVFs-1). What: /sys/bus/pci/devices/.../dep_link Date: March 2009 Contact: Yu Zhao <yu.zhao@intel.com> Description: This symbolic link appears when hardware supports the SR-IOV capability and the Physical Function driver has enabled it, and this device has vendor specific dependencies with others. The symbolic link points to the PCI device sysfs entry of Physical Function this device depends on. What: /sys/bus/pci/devices/.../physfn Date: March 2009 Contact: Yu Zhao <yu.zhao@intel.com> Description: This symbolic link appears when a device is a Virtual Function. The symbolic link points to the PCI device sysfs entry of the Physical Function this device associates with. Documentation/ABI/testing/sysfs-fs-ext4 0 → 100644 +81 −0 Original line number Diff line number Diff line What: /sys/fs/ext4/<disk>/mb_stats Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: Controls whether the multiblock allocator should collect statistics, which are shown during the unmount. 1 means to collect statistics, 0 means not to collect statistics What: /sys/fs/ext4/<disk>/mb_group_prealloc Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: The multiblock allocator will round up allocation requests to a multiple of this tuning parameter if the stripe size is not set in the ext4 superblock What: /sys/fs/ext4/<disk>/mb_max_to_scan Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: The maximum number of extents the multiblock allocator will search to find the best extent What: /sys/fs/ext4/<disk>/mb_min_to_scan Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: The minimum number of extents the multiblock allocator will search to find the best extent What: /sys/fs/ext4/<disk>/mb_order2_req Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: Tuning parameter which controls the minimum size for requests (as a power of 2) where the buddy cache is used What: /sys/fs/ext4/<disk>/mb_stream_req Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: Files which have fewer blocks than this tunable parameter will have their blocks allocated out of a block group specific preallocation pool, so that small files are packed closely together. Each large file will have its blocks allocated out of its own unique preallocation pool. What: /sys/fs/ext4/<disk>/inode_readahead Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: Tuning parameter which controls the maximum number of inode table blocks that ext4's inode table readahead algorithm will pre-read into the buffer cache What: /sys/fs/ext4/<disk>/delayed_allocation_blocks Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: This file is read-only and shows the number of blocks that are dirty in the page cache, but which do not have their location in the filesystem allocated yet. What: /sys/fs/ext4/<disk>/lifetime_write_kbytes Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: This file is read-only and shows the number of kilobytes of data that have been written to this filesystem since it was created. What: /sys/fs/ext4/<disk>/session_write_kbytes Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: This file is read-only and shows the number of kilobytes of data that have been written to this filesystem since it was mounted. Documentation/DocBook/kernel-api.tmpl +1 −0 Original line number Diff line number Diff line Loading @@ -199,6 +199,7 @@ X!Edrivers/pci/hotplug.c --> !Edrivers/pci/probe.c !Edrivers/pci/rom.c !Edrivers/pci/iov.c </sect1> <sect1><title>PCI Hotplug Support Library</title> !Edrivers/pci/hotplug/pci_hotplug_core.c Loading Documentation/DocBook/procfs_example.c +0 −9 Original line number Diff line number Diff line Loading @@ -117,9 +117,6 @@ static int __init init_procfs_example(void) rv = -ENOMEM; goto out; } example_dir->owner = THIS_MODULE; /* create jiffies using convenience function */ jiffies_file = create_proc_read_entry("jiffies", 0444, example_dir, Loading @@ -130,8 +127,6 @@ static int __init init_procfs_example(void) goto no_jiffies; } jiffies_file->owner = THIS_MODULE; /* create foo and bar files using same callback * functions */ Loading @@ -146,7 +141,6 @@ static int __init init_procfs_example(void) foo_file->data = &foo_data; foo_file->read_proc = proc_read_foobar; foo_file->write_proc = proc_write_foobar; foo_file->owner = THIS_MODULE; bar_file = create_proc_entry("bar", 0644, example_dir); if(bar_file == NULL) { Loading @@ -159,7 +153,6 @@ static int __init init_procfs_example(void) bar_file->data = &bar_data; bar_file->read_proc = proc_read_foobar; bar_file->write_proc = proc_write_foobar; bar_file->owner = THIS_MODULE; /* create symlink */ symlink = proc_symlink("jiffies_too", example_dir, Loading @@ -169,8 +162,6 @@ static int __init init_procfs_example(void) goto no_symlink; } symlink->owner = THIS_MODULE; /* everything OK */ printk(KERN_INFO "%s %s initialised\n", MODULE_NAME, MODULE_VERS); Loading Loading
CREDITS +9 −0 Original line number Diff line number Diff line Loading @@ -495,6 +495,11 @@ S: Kopmansg 2 S: 411 13 Goteborg S: Sweden N: Paul Bristow E: paul@paulbristow.net W: http://paulbristow.net/linux/idefloppy.html D: Maintainer of IDE/ATAPI floppy driver N: Dominik Brodowski E: linux@brodo.de W: http://www.brodo.de/ Loading Loading @@ -2642,6 +2647,10 @@ S: C/ Mieses 20, 9-B S: Valladolid 47009 S: Spain N: Gadi Oxman E: gadio@netvision.net.il D: Original author and maintainer of IDE/ATAPI floppy/tape drivers N: Greg Page E: gpage@sovereign.org D: IPX development and support Loading
Documentation/ABI/testing/sysfs-bus-pci +70 −0 Original line number Diff line number Diff line Loading @@ -41,6 +41,49 @@ Description: for the device and attempt to bind to it. For example: # echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id What: /sys/bus/pci/drivers/.../remove_id Date: February 2009 Contact: Chris Wright <chrisw@sous-sol.org> Description: Writing a device ID to this file will remove an ID that was dynamically added via the new_id sysfs entry. The format for the device ID is: VVVV DDDD SVVV SDDD CCCC MMMM. That is Vendor ID, Device ID, Subsystem Vendor ID, Subsystem Device ID, Class, and Class Mask. The Vendor ID and Device ID fields are required, the rest are optional. After successfully removing an ID, the driver will no longer support the device. This is useful to ensure auto probing won't match the driver to the device. For example: # echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id What: /sys/bus/pci/rescan Date: January 2009 Contact: Linux PCI developers <linux-pci@vger.kernel.org> Description: Writing a non-zero value to this attribute will force a rescan of all PCI buses in the system, and re-discover previously removed devices. Depends on CONFIG_HOTPLUG. What: /sys/bus/pci/devices/.../remove Date: January 2009 Contact: Linux PCI developers <linux-pci@vger.kernel.org> Description: Writing a non-zero value to this attribute will hot-remove the PCI device and any of its children. Depends on CONFIG_HOTPLUG. What: /sys/bus/pci/devices/.../rescan Date: January 2009 Contact: Linux PCI developers <linux-pci@vger.kernel.org> Description: Writing a non-zero value to this attribute will force a rescan of the device's parent bus and all child buses, and re-discover devices removed earlier from this part of the device tree. Depends on CONFIG_HOTPLUG. What: /sys/bus/pci/devices/.../vpd Date: February 2008 Contact: Ben Hutchings <bhutchings@solarflare.com> Loading @@ -52,3 +95,30 @@ Description: that some devices may have malformatted data. If the underlying VPD has a writable section then the corresponding section of this file will be writable. What: /sys/bus/pci/devices/.../virtfnN Date: March 2009 Contact: Yu Zhao <yu.zhao@intel.com> Description: This symbolic link appears when hardware supports the SR-IOV capability and the Physical Function driver has enabled it. The symbolic link points to the PCI device sysfs entry of the Virtual Function whose index is N (0...MaxVFs-1). What: /sys/bus/pci/devices/.../dep_link Date: March 2009 Contact: Yu Zhao <yu.zhao@intel.com> Description: This symbolic link appears when hardware supports the SR-IOV capability and the Physical Function driver has enabled it, and this device has vendor specific dependencies with others. The symbolic link points to the PCI device sysfs entry of Physical Function this device depends on. What: /sys/bus/pci/devices/.../physfn Date: March 2009 Contact: Yu Zhao <yu.zhao@intel.com> Description: This symbolic link appears when a device is a Virtual Function. The symbolic link points to the PCI device sysfs entry of the Physical Function this device associates with.
Documentation/ABI/testing/sysfs-fs-ext4 0 → 100644 +81 −0 Original line number Diff line number Diff line What: /sys/fs/ext4/<disk>/mb_stats Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: Controls whether the multiblock allocator should collect statistics, which are shown during the unmount. 1 means to collect statistics, 0 means not to collect statistics What: /sys/fs/ext4/<disk>/mb_group_prealloc Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: The multiblock allocator will round up allocation requests to a multiple of this tuning parameter if the stripe size is not set in the ext4 superblock What: /sys/fs/ext4/<disk>/mb_max_to_scan Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: The maximum number of extents the multiblock allocator will search to find the best extent What: /sys/fs/ext4/<disk>/mb_min_to_scan Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: The minimum number of extents the multiblock allocator will search to find the best extent What: /sys/fs/ext4/<disk>/mb_order2_req Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: Tuning parameter which controls the minimum size for requests (as a power of 2) where the buddy cache is used What: /sys/fs/ext4/<disk>/mb_stream_req Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: Files which have fewer blocks than this tunable parameter will have their blocks allocated out of a block group specific preallocation pool, so that small files are packed closely together. Each large file will have its blocks allocated out of its own unique preallocation pool. What: /sys/fs/ext4/<disk>/inode_readahead Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: Tuning parameter which controls the maximum number of inode table blocks that ext4's inode table readahead algorithm will pre-read into the buffer cache What: /sys/fs/ext4/<disk>/delayed_allocation_blocks Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: This file is read-only and shows the number of blocks that are dirty in the page cache, but which do not have their location in the filesystem allocated yet. What: /sys/fs/ext4/<disk>/lifetime_write_kbytes Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: This file is read-only and shows the number of kilobytes of data that have been written to this filesystem since it was created. What: /sys/fs/ext4/<disk>/session_write_kbytes Date: March 2008 Contact: "Theodore Ts'o" <tytso@mit.edu> Description: This file is read-only and shows the number of kilobytes of data that have been written to this filesystem since it was mounted.
Documentation/DocBook/kernel-api.tmpl +1 −0 Original line number Diff line number Diff line Loading @@ -199,6 +199,7 @@ X!Edrivers/pci/hotplug.c --> !Edrivers/pci/probe.c !Edrivers/pci/rom.c !Edrivers/pci/iov.c </sect1> <sect1><title>PCI Hotplug Support Library</title> !Edrivers/pci/hotplug/pci_hotplug_core.c Loading
Documentation/DocBook/procfs_example.c +0 −9 Original line number Diff line number Diff line Loading @@ -117,9 +117,6 @@ static int __init init_procfs_example(void) rv = -ENOMEM; goto out; } example_dir->owner = THIS_MODULE; /* create jiffies using convenience function */ jiffies_file = create_proc_read_entry("jiffies", 0444, example_dir, Loading @@ -130,8 +127,6 @@ static int __init init_procfs_example(void) goto no_jiffies; } jiffies_file->owner = THIS_MODULE; /* create foo and bar files using same callback * functions */ Loading @@ -146,7 +141,6 @@ static int __init init_procfs_example(void) foo_file->data = &foo_data; foo_file->read_proc = proc_read_foobar; foo_file->write_proc = proc_write_foobar; foo_file->owner = THIS_MODULE; bar_file = create_proc_entry("bar", 0644, example_dir); if(bar_file == NULL) { Loading @@ -159,7 +153,6 @@ static int __init init_procfs_example(void) bar_file->data = &bar_data; bar_file->read_proc = proc_read_foobar; bar_file->write_proc = proc_write_foobar; bar_file->owner = THIS_MODULE; /* create symlink */ symlink = proc_symlink("jiffies_too", example_dir, Loading @@ -169,8 +162,6 @@ static int __init init_procfs_example(void) goto no_symlink; } symlink->owner = THIS_MODULE; /* everything OK */ printk(KERN_INFO "%s %s initialised\n", MODULE_NAME, MODULE_VERS); Loading
