Fix typos in /Documentation : 'U-Z'

flags can be or'd together and are

DMA_MEMORY_MAP - request that the memory returned from

dma_alloc_coherent() be directly writeable.

dma_alloc_coherent() be directly writable.

DMA_MEMORY_IO - request that the memory returned from

dma_alloc_coherent() be addressable using read/write/memcpy_toio etc.

Note that the pre-assigned IOAPIC dev->irq is valid only if the device

operates in PIN-IRQ assertion mode. In MSI-X mode, any attempt at

using dev->irq by the device driver to request for interrupt service

may result unpredictabe behavior.

may result in unpredictable behavior.

For each MSI-X vector granted, a device driver is responsible for calling

other functions like request_irq(), enable_irq(), etc. to enable

However, maintaining per-process, in addition to per-task stats, within the

kernel has space and time overheads. To address this, the taskstats code

accumalates each exiting task's statistics into a process-wide data structure.

When the last task of a process exits, the process level data accumalated also

accumulates each exiting task's statistics into a process-wide data structure.

When the last task of a process exits, the process level data accumulated also

gets sent to userspace (along with the per-task data).

When a user queries to get per-tgid data, the sum of all other live threads in

the group is added up and added to the accumalated total for previously exited

the group is added up and added to the accumulated total for previously exited

threads of the same thread group.

Extending taskstats

on to the generic block layer, only to be merged by the i/o scheduler

when the underlying device was capable of handling the i/o in one shot.

Also, using the buffer head as an i/o structure for i/os that didn't originate

from the buffer cache unecessarily added to the weight of the descriptors

from the buffer cache unnecessarily added to the weight of the descriptors

which were generated for each such chunk.

The following were some of the goals and expectations considered in the

    for raw i/o.

ii. Ability to represent high-memory buffers (which do not have a virtual

    address mapping in kernel address space).

iii.Ability to represent large i/os w/o unecessarily breaking them up (i.e

iii.Ability to represent large i/os w/o unnecessarily breaking them up (i.e

    greater than PAGE_SIZE chunks in one shot)

iv. At the same time, ability to retain independent identity of i/os from

    different sources or i/o units requiring individual completion (e.g. for

    latency reasons)

v.  Ability to represent an i/o involving multiple physical memory segments

    (including non-page aligned page fragments, as specified via readv/writev)

    without unecessarily breaking it up, if the underlying device is capable of

    without unnecessarily breaking it up, if the underlying device is capable of

    handling it.

vi. Preferably should be based on a memory descriptor structure that can be

    passed around different types of subsystems or layers, maybe even

The disadvantage is that the driver/hardware has to manage the rest. For

the application programmer it would be as simple as sending/receiving an

array to/from the CI ioctls as defined in the Linux DVB API. No changes

have been made in the API to accomodate this feature.

have been made in the API to accommodate this feature.

* Why the need for another CI interface ?

implemented by most applications. Hence this area is revisited.

This CI interface is quite different in the case that it tries to

accomodate all other CI based devices, that fall into the other categories

accommodate all other CI based devices, that fall into the other categories.

This means that this CI interface handles the EN50221 style tags in the

Application layer only and no session management is taken care of by the