Loading Documentation/RCU/checklist.txt +12 −0 Original line number Diff line number Diff line Loading @@ -298,3 +298,15 @@ over a rather long period of time, but improvements are always welcome! Note that, rcu_assign_pointer() and rcu_dereference() relate to SRCU just as they do to other forms of RCU. 15. The whole point of call_rcu(), synchronize_rcu(), and friends is to wait until all pre-existing readers have finished before carrying out some otherwise-destructive operation. It is therefore critically important to -first- remove any path that readers can follow that could be affected by the destructive operation, and -only- -then- invoke call_rcu(), synchronize_rcu(), or friends. Because these primitives only wait for pre-existing readers, it is the caller's responsibility to guarantee safety to any subsequent readers. Documentation/feature-removal-schedule.txt +9 −0 Original line number Diff line number Diff line Loading @@ -335,3 +335,12 @@ Why: In 2.6.18 the Secmark concept was introduced to replace the "compat_net" Secmark, it is time to deprecate the older mechanism and start the process of removing the old code. Who: Paul Moore <paul.moore@hp.com> --------------------------- What: sysfs ui for changing p4-clockmod parameters When: September 2009 Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and e088e4c9cdb618675874becb91b2fd581ee707e6. Removal is subject to fixing any remaining bugs in ACPI which may cause the thermal throttling not to happen at the right time. Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com> Documentation/filesystems/squashfs.txt +1 −1 Original line number Diff line number Diff line Loading @@ -22,7 +22,7 @@ Squashfs filesystem features versus Cramfs: Squashfs Cramfs Max filesystem size: 2^64 16 MiB Max filesystem size: 2^64 256 MiB Max file size: ~ 2 TiB 16 MiB Max files: unlimited unlimited Max directories: unlimited unlimited Loading Documentation/networking/ipv6.txt 0 → 100644 +35 −0 Original line number Diff line number Diff line Options for the ipv6 module are supplied as parameters at load time. Module options may be given as command line arguments to the insmod or modprobe command, but are usually specified in either the /etc/modules.conf or /etc/modprobe.conf configuration file, or in a distro-specific configuration file. The available ipv6 module parameters are listed below. If a parameter is not specified the default value is used. The parameters are as follows: disable Specifies whether to load the IPv6 module, but disable all its functionality. This might be used when another module has a dependency on the IPv6 module being loaded, but no IPv6 addresses or operations are desired. The possible values and their effects are: 0 IPv6 is enabled. This is the default value. 1 IPv6 is disabled. No IPv6 addresses will be added to interfaces, and it will not be possible to open an IPv6 socket. A reboot is required to enable IPv6. Documentation/scsi/cxgb3i.txt +5 −6 Original line number Diff line number Diff line Loading @@ -4,7 +4,7 @@ Introduction ============ The Chelsio T3 ASIC based Adapters (S310, S320, S302, S304, Mezz cards, etc. series of products) supports iSCSI acceleration and iSCSI Direct Data Placement series of products) support iSCSI acceleration and iSCSI Direct Data Placement (DDP) where the hardware handles the expensive byte touching operations, such as CRC computation and verification, and direct DMA to the final host memory destination: Loading @@ -31,9 +31,9 @@ destination: the TCP segments onto the wire. It handles TCP retransmission if needed. On receving, S3 h/w recovers the iSCSI PDU by reassembling TCP On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP segments, separating the header and data, calculating and verifying the digests, then forwards the header to the host. The payload data, the digests, then forwarding the header to the host. The payload data, if possible, will be directly placed into the pre-posted host DDP buffer. Otherwise, the payload data will be sent to the host too. Loading Loading @@ -68,9 +68,8 @@ The following steps need to be taken to accelerates the open-iscsi initiator: sure the ip address is unique in the network. 3. edit /etc/iscsi/iscsid.conf The default setting for MaxRecvDataSegmentLength (131072) is too big, replace "node.conn[0].iscsi.MaxRecvDataSegmentLength" to be a value no bigger than 15360 (for example 8192): The default setting for MaxRecvDataSegmentLength (131072) is too big; replace with a value no bigger than 15360 (for example 8192): node.conn[0].iscsi.MaxRecvDataSegmentLength = 8192 Loading Loading
Documentation/RCU/checklist.txt +12 −0 Original line number Diff line number Diff line Loading @@ -298,3 +298,15 @@ over a rather long period of time, but improvements are always welcome! Note that, rcu_assign_pointer() and rcu_dereference() relate to SRCU just as they do to other forms of RCU. 15. The whole point of call_rcu(), synchronize_rcu(), and friends is to wait until all pre-existing readers have finished before carrying out some otherwise-destructive operation. It is therefore critically important to -first- remove any path that readers can follow that could be affected by the destructive operation, and -only- -then- invoke call_rcu(), synchronize_rcu(), or friends. Because these primitives only wait for pre-existing readers, it is the caller's responsibility to guarantee safety to any subsequent readers.
Documentation/feature-removal-schedule.txt +9 −0 Original line number Diff line number Diff line Loading @@ -335,3 +335,12 @@ Why: In 2.6.18 the Secmark concept was introduced to replace the "compat_net" Secmark, it is time to deprecate the older mechanism and start the process of removing the old code. Who: Paul Moore <paul.moore@hp.com> --------------------------- What: sysfs ui for changing p4-clockmod parameters When: September 2009 Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and e088e4c9cdb618675874becb91b2fd581ee707e6. Removal is subject to fixing any remaining bugs in ACPI which may cause the thermal throttling not to happen at the right time. Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com>
Documentation/filesystems/squashfs.txt +1 −1 Original line number Diff line number Diff line Loading @@ -22,7 +22,7 @@ Squashfs filesystem features versus Cramfs: Squashfs Cramfs Max filesystem size: 2^64 16 MiB Max filesystem size: 2^64 256 MiB Max file size: ~ 2 TiB 16 MiB Max files: unlimited unlimited Max directories: unlimited unlimited Loading
Documentation/networking/ipv6.txt 0 → 100644 +35 −0 Original line number Diff line number Diff line Options for the ipv6 module are supplied as parameters at load time. Module options may be given as command line arguments to the insmod or modprobe command, but are usually specified in either the /etc/modules.conf or /etc/modprobe.conf configuration file, or in a distro-specific configuration file. The available ipv6 module parameters are listed below. If a parameter is not specified the default value is used. The parameters are as follows: disable Specifies whether to load the IPv6 module, but disable all its functionality. This might be used when another module has a dependency on the IPv6 module being loaded, but no IPv6 addresses or operations are desired. The possible values and their effects are: 0 IPv6 is enabled. This is the default value. 1 IPv6 is disabled. No IPv6 addresses will be added to interfaces, and it will not be possible to open an IPv6 socket. A reboot is required to enable IPv6.
Documentation/scsi/cxgb3i.txt +5 −6 Original line number Diff line number Diff line Loading @@ -4,7 +4,7 @@ Introduction ============ The Chelsio T3 ASIC based Adapters (S310, S320, S302, S304, Mezz cards, etc. series of products) supports iSCSI acceleration and iSCSI Direct Data Placement series of products) support iSCSI acceleration and iSCSI Direct Data Placement (DDP) where the hardware handles the expensive byte touching operations, such as CRC computation and verification, and direct DMA to the final host memory destination: Loading @@ -31,9 +31,9 @@ destination: the TCP segments onto the wire. It handles TCP retransmission if needed. On receving, S3 h/w recovers the iSCSI PDU by reassembling TCP On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP segments, separating the header and data, calculating and verifying the digests, then forwards the header to the host. The payload data, the digests, then forwarding the header to the host. The payload data, if possible, will be directly placed into the pre-posted host DDP buffer. Otherwise, the payload data will be sent to the host too. Loading Loading @@ -68,9 +68,8 @@ The following steps need to be taken to accelerates the open-iscsi initiator: sure the ip address is unique in the network. 3. edit /etc/iscsi/iscsid.conf The default setting for MaxRecvDataSegmentLength (131072) is too big, replace "node.conn[0].iscsi.MaxRecvDataSegmentLength" to be a value no bigger than 15360 (for example 8192): The default setting for MaxRecvDataSegmentLength (131072) is too big; replace with a value no bigger than 15360 (for example 8192): node.conn[0].iscsi.MaxRecvDataSegmentLength = 8192 Loading
