Lines Matching refs:Target

451 the Queue Depth and whether Tagged Queuing is permitted for each Target
452 Device (assuming that the Target Device supports Tagged Queuing).  The Queue
454 presented for execution (either to the Host Adapter or Target Device).  Note
457 Tagged Queuing on Target Devices that do not implement it correctly.  The
463   Target Devices that support Tagged Queuing, as well as the maximum Queue
467   capabilities of the detected Target Devices.  For Host Adapters that
470   excessive preallocation of DMA Bounce Buffer memory.  Target Devices that
479   individually for each Target Device.  If an <integer> is omitted, the
480   associated Target Device will have its Queue Depth selected automatically.
491   all Target Devices on this Host Adapter, overriding any limitation that
497   for all Target Devices on this Host Adapter.
499 TaggedQueuing:<Target-Spec>
501   The "TaggedQueuing:<Target-Spec>" or "TQ:<Target-Spec>" option controls
502   Tagged Queuing individually for each Target Device.  <Target-Spec> is a
505   version.  The first character refers to Target Device 0, the second to
506   Target Device 1, and so on; if the sequence of "Y", "N", and "X" characters
507   does not cover all the Target Devices, unspecified characters are assumed
522   Target Devices or Inquire Installed Devices command on MultiMaster Host
523   Adapters.  This may be necessary with some older Target Devices that do not
545   error from the Target Device.  The CDB and Sense Data will be printed for
552 The following examples demonstrate setting the Queue Depth for Target Devices
553 1 and 2 on the first host adapter to 7 and 15, the Queue Depth for all Target