Lines Matching refs:Target

417 the Queue Depth and whether Tagged Queuing is permitted for each Target
418 Device (assuming that the Target Device supports Tagged Queuing).  The Queue
420 presented for execution (either to the Host Adapter or Target Device).  Note
423 Tagged Queuing on Target Devices that do not implement it correctly.  The
429   Target Devices that support Tagged Queuing, as well as the maximum Queue
433   capabilities of the detected Target Devices.  For Host Adapters that
436   excessive preallocation of DMA Bounce Buffer memory.  Target Devices that
445   individually for each Target Device.  If an <integer> is omitted, the
446   associated Target Device will have its Queue Depth selected automatically.
457   all Target Devices on this Host Adapter, overriding any limitation that
463   for all Target Devices on this Host Adapter.
465 TaggedQueuing:<Target-Spec>
467   The "TaggedQueuing:<Target-Spec>" or "TQ:<Target-Spec>" option controls
468   Tagged Queuing individually for each Target Device.  <Target-Spec> is a
471   version.  The first character refers to Target Device 0, the second to
472   Target Device 1, and so on; if the sequence of "Y", "N", and "X" characters
473   does not cover all the Target Devices, unspecified characters are assumed
488   Target Devices or Inquire Installed Devices command on MultiMaster Host
489   Adapters.  This may be necessary with some older Target Devices that do not
511   error from the Target Device.  The CDB and Sense Data will be printed for
518 The following examples demonstrate setting the Queue Depth for Target Devices
519 1 and 2 on the first host adapter to 7 and 15, the Queue Depth for all Target