Loading Documentation/cpu-hotplug.txt +24 −3 Original line number Diff line number Diff line Loading @@ -11,6 +11,8 @@ Joel Schopp <jschopp@austin.ibm.com> ia64/x86_64: Ashok Raj <ashok.raj@intel.com> s390: Heiko Carstens <heiko.carstens@de.ibm.com> Authors: Ashok Raj <ashok.raj@intel.com> Lots of feedback: Nathan Lynch <nathanl@austin.ibm.com>, Loading Loading @@ -44,10 +46,29 @@ maxcpus=n Restrict boot time cpus to n. Say if you have 4 cpus, using maxcpus=2 will only boot 2. You can choose to bring the other cpus later online, read FAQ's for more info. additional_cpus=n [x86_64 only] use this to limit hotpluggable cpus. This option sets additional_cpus*=n Use this to limit hotpluggable cpus. This option sets cpu_possible_map = cpu_present_map + additional_cpus (*) Option valid only for following architectures - x86_64, ia64, s390 ia64 and x86_64 use the number of disabled local apics in ACPI tables MADT to determine the number of potentially hot-pluggable cpus. The implementation should only rely on this to count the #of cpus, but *MUST* not rely on the apicid values in those tables for disabled apics. In the event BIOS doesnt mark such hot-pluggable cpus as disabled entries, one could use this parameter "additional_cpus=x" to represent those cpus in the cpu_possible_map. s390 uses the number of cpus it detects at IPL time to also the number of bits in cpu_possible_map. If it is desired to add additional cpus at a later time the number should be specified using this option or the possible_cpus option. possible_cpus=n [s390 only] use this to set hotpluggable cpus. This option sets possible_cpus bits in cpu_possible_map. Thus keeping the numbers of bits set constant even if the machine gets rebooted. This option overrides additional_cpus. CPU maps and such ----------------- [More on cpumaps and primitive to manipulate, please check Loading Documentation/feature-removal-schedule.txt +9 −0 Original line number Diff line number Diff line Loading @@ -178,3 +178,12 @@ Why: The ISA interface is faster and should be always available. The I2C probing is also known to cause trouble in at least one case (see bug #5889.) Who: Jean Delvare <khali@linux-fr.org> --------------------------- What: mount/umount uevents When: February 2007 Why: These events are not correct, and do not properly let userspace know when a file system has been mounted or unmounted. Userspace should poll the /proc/mounts file instead to detect this properly. Who: Greg Kroah-Hartman <gregkh@suse.de> Documentation/filesystems/ntfs.txt +6 −0 Original line number Diff line number Diff line Loading @@ -457,6 +457,12 @@ ChangeLog Note, a technical ChangeLog aimed at kernel hackers is in fs/ntfs/ChangeLog. 2.1.26: - Implement support for sector sizes above 512 bytes (up to the maximum supported by NTFS which is 4096 bytes). - Enhance support for NTFS volumes which were supported by Windows but not by Linux due to invalid attribute list attribute flags. - A few minor updates and bug fixes. 2.1.25: - Write support is now extended with write(2) being able to both overwrite existing file data and to extend files. Also, if a write Loading Documentation/filesystems/tmpfs.txt +21 −9 Original line number Diff line number Diff line Loading @@ -79,15 +79,27 @@ that instance in a system with many cpus making intensive use of it. tmpfs has a mount option to set the NUMA memory allocation policy for all files in that instance: mpol=interleave prefers to allocate memory from each node in turn all files in that instance (if CONFIG_NUMA is enabled) - which can be adjusted on the fly via 'mount -o remount ...' mpol=default prefers to allocate memory from the local node mpol=bind prefers to allocate from mpol_nodelist mpol=preferred prefers to allocate from first node in mpol_nodelist mpol=prefer:Node prefers to allocate memory from the given Node mpol=bind:NodeList allocates memory only from nodes in NodeList mpol=interleave prefers to allocate from each node in turn mpol=interleave:NodeList allocates from each node of NodeList in turn NodeList format is a comma-separated list of decimal numbers and ranges, a range being two hyphen-separated decimal numbers, the smallest and largest node numbers in the range. For example, mpol=bind:0-3,5,7,9-15 The following mount option is used in conjunction with mpol=interleave, mpol=bind or mpol=preferred: mpol_nodelist: nodelist suitable for parsing with nodelist_parse. Note that trying to mount a tmpfs with an mpol option will fail if the running kernel does not support NUMA; and will fail if its nodelist specifies a node >= MAX_NUMNODES. If your system relies on that tmpfs being mounted, but from time to time runs a kernel built without NUMA capability (perhaps a safe recovery kernel), or configured to support fewer nodes, then it is advisable to omit the mpol option from automatic mount options. It can be added later, when the tmpfs is already mounted on MountPoint, by 'mount -o remount,mpol=Policy:NodeList MountPoint'. To specify the initial root directory you can use the following mount Loading @@ -109,4 +121,4 @@ RAM/SWAP in 10240 inodes and it is only accessible by root. Author: Christoph Rohland <cr@sap.com>, 1.12.01 Updated: Hugh Dickins <hugh@veritas.com>, 13 March 2005 Hugh Dickins <hugh@veritas.com>, 19 February 2006 Documentation/filesystems/v9fs.txt +10 −6 Original line number Diff line number Diff line Loading @@ -57,8 +57,6 @@ OPTIONS port=n port to connect to on the remote server timeout=n request timeouts (in ms) (default 60000ms) noextend force legacy mode (no 9P2000.u semantics) uid attempt to mount as a particular uid Loading @@ -74,10 +72,16 @@ OPTIONS RESOURCES ========= The Linux version of the 9P server, along with some client-side utilities can be found at http://v9fs.sf.net (along with a CVS repository of the development branch of this module). There are user and developer mailing lists here, as well as a bug-tracker. The Linux version of the 9P server is now maintained under the npfs project on sourceforge (http://sourceforge.net/projects/npfs). There are user and developer mailing lists available through the v9fs project on sourceforge (http://sourceforge.net/projects/v9fs). News and other information is maintained on SWiK (http://swik.net/v9fs). Bug reports may be issued through the kernel.org bugzilla (http://bugzilla.kernel.org) For more information on the Plan 9 Operating System check out http://plan9.bell-labs.com/plan9 Loading Loading
Documentation/cpu-hotplug.txt +24 −3 Original line number Diff line number Diff line Loading @@ -11,6 +11,8 @@ Joel Schopp <jschopp@austin.ibm.com> ia64/x86_64: Ashok Raj <ashok.raj@intel.com> s390: Heiko Carstens <heiko.carstens@de.ibm.com> Authors: Ashok Raj <ashok.raj@intel.com> Lots of feedback: Nathan Lynch <nathanl@austin.ibm.com>, Loading Loading @@ -44,10 +46,29 @@ maxcpus=n Restrict boot time cpus to n. Say if you have 4 cpus, using maxcpus=2 will only boot 2. You can choose to bring the other cpus later online, read FAQ's for more info. additional_cpus=n [x86_64 only] use this to limit hotpluggable cpus. This option sets additional_cpus*=n Use this to limit hotpluggable cpus. This option sets cpu_possible_map = cpu_present_map + additional_cpus (*) Option valid only for following architectures - x86_64, ia64, s390 ia64 and x86_64 use the number of disabled local apics in ACPI tables MADT to determine the number of potentially hot-pluggable cpus. The implementation should only rely on this to count the #of cpus, but *MUST* not rely on the apicid values in those tables for disabled apics. In the event BIOS doesnt mark such hot-pluggable cpus as disabled entries, one could use this parameter "additional_cpus=x" to represent those cpus in the cpu_possible_map. s390 uses the number of cpus it detects at IPL time to also the number of bits in cpu_possible_map. If it is desired to add additional cpus at a later time the number should be specified using this option or the possible_cpus option. possible_cpus=n [s390 only] use this to set hotpluggable cpus. This option sets possible_cpus bits in cpu_possible_map. Thus keeping the numbers of bits set constant even if the machine gets rebooted. This option overrides additional_cpus. CPU maps and such ----------------- [More on cpumaps and primitive to manipulate, please check Loading
Documentation/feature-removal-schedule.txt +9 −0 Original line number Diff line number Diff line Loading @@ -178,3 +178,12 @@ Why: The ISA interface is faster and should be always available. The I2C probing is also known to cause trouble in at least one case (see bug #5889.) Who: Jean Delvare <khali@linux-fr.org> --------------------------- What: mount/umount uevents When: February 2007 Why: These events are not correct, and do not properly let userspace know when a file system has been mounted or unmounted. Userspace should poll the /proc/mounts file instead to detect this properly. Who: Greg Kroah-Hartman <gregkh@suse.de>
Documentation/filesystems/ntfs.txt +6 −0 Original line number Diff line number Diff line Loading @@ -457,6 +457,12 @@ ChangeLog Note, a technical ChangeLog aimed at kernel hackers is in fs/ntfs/ChangeLog. 2.1.26: - Implement support for sector sizes above 512 bytes (up to the maximum supported by NTFS which is 4096 bytes). - Enhance support for NTFS volumes which were supported by Windows but not by Linux due to invalid attribute list attribute flags. - A few minor updates and bug fixes. 2.1.25: - Write support is now extended with write(2) being able to both overwrite existing file data and to extend files. Also, if a write Loading
Documentation/filesystems/tmpfs.txt +21 −9 Original line number Diff line number Diff line Loading @@ -79,15 +79,27 @@ that instance in a system with many cpus making intensive use of it. tmpfs has a mount option to set the NUMA memory allocation policy for all files in that instance: mpol=interleave prefers to allocate memory from each node in turn all files in that instance (if CONFIG_NUMA is enabled) - which can be adjusted on the fly via 'mount -o remount ...' mpol=default prefers to allocate memory from the local node mpol=bind prefers to allocate from mpol_nodelist mpol=preferred prefers to allocate from first node in mpol_nodelist mpol=prefer:Node prefers to allocate memory from the given Node mpol=bind:NodeList allocates memory only from nodes in NodeList mpol=interleave prefers to allocate from each node in turn mpol=interleave:NodeList allocates from each node of NodeList in turn NodeList format is a comma-separated list of decimal numbers and ranges, a range being two hyphen-separated decimal numbers, the smallest and largest node numbers in the range. For example, mpol=bind:0-3,5,7,9-15 The following mount option is used in conjunction with mpol=interleave, mpol=bind or mpol=preferred: mpol_nodelist: nodelist suitable for parsing with nodelist_parse. Note that trying to mount a tmpfs with an mpol option will fail if the running kernel does not support NUMA; and will fail if its nodelist specifies a node >= MAX_NUMNODES. If your system relies on that tmpfs being mounted, but from time to time runs a kernel built without NUMA capability (perhaps a safe recovery kernel), or configured to support fewer nodes, then it is advisable to omit the mpol option from automatic mount options. It can be added later, when the tmpfs is already mounted on MountPoint, by 'mount -o remount,mpol=Policy:NodeList MountPoint'. To specify the initial root directory you can use the following mount Loading @@ -109,4 +121,4 @@ RAM/SWAP in 10240 inodes and it is only accessible by root. Author: Christoph Rohland <cr@sap.com>, 1.12.01 Updated: Hugh Dickins <hugh@veritas.com>, 13 March 2005 Hugh Dickins <hugh@veritas.com>, 19 February 2006
Documentation/filesystems/v9fs.txt +10 −6 Original line number Diff line number Diff line Loading @@ -57,8 +57,6 @@ OPTIONS port=n port to connect to on the remote server timeout=n request timeouts (in ms) (default 60000ms) noextend force legacy mode (no 9P2000.u semantics) uid attempt to mount as a particular uid Loading @@ -74,10 +72,16 @@ OPTIONS RESOURCES ========= The Linux version of the 9P server, along with some client-side utilities can be found at http://v9fs.sf.net (along with a CVS repository of the development branch of this module). There are user and developer mailing lists here, as well as a bug-tracker. The Linux version of the 9P server is now maintained under the npfs project on sourceforge (http://sourceforge.net/projects/npfs). There are user and developer mailing lists available through the v9fs project on sourceforge (http://sourceforge.net/projects/v9fs). News and other information is maintained on SWiK (http://swik.net/v9fs). Bug reports may be issued through the kernel.org bugzilla (http://bugzilla.kernel.org) For more information on the Plan 9 Operating System check out http://plan9.bell-labs.com/plan9 Loading
