:In the last episode (Apr 26), Kent Stewart said:
:> I just noticed that mine isn't showing "Tagged Queueing Enabled" is
:> that something I can set? The adapter is an Adaptec 2940uw.
:>
:> da0 at ahc0 bus 0 target 4 lun 0
:> da0: <IBM DCAS-34330W S65A> Fixed Direct Access SCSI-2 device
:> da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
:> da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
:
:The CAM code has a quirk entry for IBM DCAS drives that turns it off;
:check out /sys/cam/cam_xpt.c, line 320. I suggest benchmarking with
:and without the quirk entry, and if it's faster with tagged queueing,
:update PR kern/10398.
:
:--
: Dan Nelson
: [EMAIL PROTECTED]
I seem to remember a discussion last year about tagged commands being
a lot slower on IBM drives being the reason why tagged queueing was
turned off. I wonder if IBM has fixed the problem in their later
drives?
Note that tagging is different from disconnection. Tagging allows
you to queue multiple commands (e.g. multiple reads & writes) to
the drive. Disconnection is a bus-level protocol which allows the
SCSI bus to be freed up after sending a command (e.g. like a read)
so other SCSI devices can use the bus while the drive is seeking.
Disconnection is more important. Tagging is nice in that it can
absorb command queueing overheads and allows the drive to prioritize
the transactions based on the characteristics of the media, but tagging
is not going to make much of a difference when you only have one or
two processes banging on the drive. Tagging shows its suds on more
heavily loaded systems, when dozens of processes are banging on the
disks.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
