Re: [PATCH 2/2] use FIFO policy instead FILO for I/O thread request handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 14 Sep 2009 11:46:37 +0300
Or Gerlitz <ogerlitz@xxxxxxxxxxxx> wrote:

> FUJITA Tomonori wrote:
> > Somehow, I/O threads perform requests in FILO manner. We should use FIFO for better performance
> Hi Tomo,
> 
> Isn't LIFO processing being a NO NO for target that eventually provides 
> block device interface towards the initiator stack... so first and most, 
> this is a bug fix, thoughts?

It's not. tgt properly handles SCSI ordering rule.

The patch is about I/O threads policy. I/O threads simultaneously
performs multiple SCSI commands that can be performed in any order.

I/O threads uses FILO so if I/O threads has tons of requests, the
latency of the first request could be large.
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux SCSI]     [Linux RAID]     [Linux Clusters]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]

  Powered by Linux