fix typos "wich" -> "which"

..............................................................................

 File    Content                                        

 cmdline Command line arguments                         

 cpu	 Current and last cpu in wich it was executed		(2.4)(smp)

 cpu	 Current and last cpu in which it was executed		(2.4)(smp)

 cwd	 Link to the current working directory

 environ Values of environment variables      

 exe	 Link to the executable of this process

  > cat /proc/irq/0/smp_affinity 

  ffffffff

It's a bitmask, in wich you can specify wich CPUs can handle the IRQ, you can

It's a bitmask, in which you can specify which CPUs can handle the IRQ, you can

set it by doing:

  > echo 1 > /proc/irq/prof_cpu_mask

This means that only the first CPU will handle the IRQ, but you can also echo 5

wich means that only the first and fourth CPU can handle the IRQ.

which means that only the first and fourth CPU can handle the IRQ.

The way IRQs are routed is handled by the IO-APIC, and it's Round Robin

between all the CPUs which are allowed to handle it. As usual the kernel has

+ How to use CONFIG_PACKET_MMAP

--------------------------------------------------------------------------------

From the user standpoint, you should use the higher level libpcap library, wich

From the user standpoint, you should use the higher level libpcap library, which

is a de facto standard, portable across nearly all operating systems

including Win32. 

kmalloc allocates any number of bytes of phisically contiguous memory from 

a pool of pre-determined sizes. This pool of memory is mantained by the slab 

allocator wich is at the end the responsible for doing the allocation and 

hence wich imposes the maximum memory that kmalloc can allocate. 

allocator which is at the end the responsible for doing the allocation and 

hence which imposes the maximum memory that kmalloc can allocate. 

In a 2.4/2.6 kernel and the i386 architecture, the limit is 131072 bytes. The 

predetermined sizes that kmalloc uses can be checked in the "size-<bytes>" 

	<block number> * <block size> / <frame size>

Suposse the following parameters, wich apply for 2.6 kernel and an

Suposse the following parameters, which apply for 2.6 kernel and an

i386 architecture:

	<size-max> = 131072 bytes

                        statistics where checked with getsockopt() and

                        the PACKET_STATISTICS option.

TP_STATUS_CSUMNOTREADY: currently it's used for outgoing IP packets wich 

TP_STATUS_CSUMNOTREADY: currently it's used for outgoing IP packets which 

                        it's checksum will be done in hardware. So while 

                        reading the packet we should not try to check the 

                        checksum. 

	depends on ACPI_CUSTOM_DSDT

	default ""

	help

	  Enter the full path name to the file wich includes the AmlCode declaration.

	  Enter the full path name to the file which includes the AmlCode

	  declaration.

config ACPI_BLACKLIST_YEAR

	int "Disable ACPI for systems before Jan 1st this year" if X86_32

 *

 * stuff needed to support the Linux X.25 PLP code on top of devices that

 * can provide a lab_b service using the concap_proto mechanism.

 * This module supports a network interface wich provides lapb_sematics

 * This module supports a network interface which provides lapb_sematics

 * -- as defined in Documentation/networking/x25-iface.txt -- to

 * the upper layer and assumes that the lower layer provides a reliable

 * data link service by means of the concap_device_ops callbacks.

 * and so on). So the PSC1 is mapped to /dev/ttyPSC0, PSC2 to /dev/ttyPSC1 and

 * so on. But be warned, it's an ABSOLUTE REQUIREMENT ! This is needed mainly

 * fpr the console code : without this 1:1 mapping, at early boot time, when we

 * are parsing the kernel args console=ttyPSC?, we wouldn't know wich PSC it

 * are parsing the kernel args console=ttyPSC?, we wouldn't know which PSC it

 * will be mapped to.

 */