From: Matthew Wilcox <matthew@wil.cx>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
Luben Tuikov <ltuikov@yahoo.com>, Greg KH <greg@kroah.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tj@kernel.org" <tj@kernel.org>
Subject: Re: SCSI TMF processing; tag allocation
Date: Mon, 15 Nov 2010 07:46:12 -0700 [thread overview]
Message-ID: <20101115144612.GA6178@parisc-linux.org> (raw)
In-Reply-To: <1289831595.2233.5.camel@mulgrave.site>
On Mon, Nov 15, 2010 at 08:33:15AM -0600, James Bottomley wrote:
> Right, it's the clock algorithm to prevent tag starvation. If you have
> hands representing the first and last tag and they're never allowed to
> cross, the device can't starve any tag for too long because eventually
> it will be the only outstanding command.
>
> It's not the only algorithm however. Banging down an ordered tag every
> 200 or so commands has exactly the same effect. In fact the clock
> algorithm was what the 53c700 driver used (before it was converted to
> generic tags) and the ordered tag what aic7xxx uses.
>
> Realistically, tag starvation isn't really a problem. It was a known
> issue for 80s era hardware. I've got some of the oldest drives on the
> planet and I didn't see a problem when the clock algorithm was removed
> from 53c700.
The problem is that each driver is solving the problem in its own way
right now, which is clearly daft. And no drive manufactured in the past
fifteen years supports ordered tags anyway, so they're only a placebo
at this point.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2010-11-15 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 6:02 SCSI TMF processing; tag allocation Luben Tuikov
2010-11-13 12:37 ` Matthew Wilcox
2010-11-15 9:28 ` Jens Axboe
2010-11-15 14:33 ` James Bottomley
2010-11-15 14:40 ` Alan Cox
2010-11-15 14:53 ` James Bottomley
2010-11-15 14:46 ` Matthew Wilcox [this message]
2010-11-15 14:52 ` James Bottomley
2010-11-16 20:28 ` Vladislav Bolkhovitin
2010-11-15 18:53 ` Douglas Gilbert
2010-11-15 19:09 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101115144612.GA6178@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@HansenPartnership.com \
--cc=greg@kroah.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox