From: Linus Torvalds <torvalds@linux-foundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: Jens Axboe <jens.axboe@oracle.com>, Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: request to revert libata-convert-to-block-tagging patches
Date: Mon, 10 Nov 2008 08:03:45 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0811100800420.3468@nehalem.linux-foundation.org> (raw)
In-Reply-To: <491835FF.1060403@kernel.org>
On Mon, 10 Nov 2008, Tejun Heo wrote:
>
> I'm just a little bit nervous because libata always has had this tag 0
> for non-NCQ commands assumption and this conversion changes that, so I
> was hoping to update blk-tag such that such assumption can be guaranteed
> first and then convert libata to be on the safe side. Some controllers
> use completely different command mechanism for different protocols and
> it's much safer and more deterministic if same tag can be guaranteed.
Yeah, I think that's a good argument. Even when controllers expect tags,
it's certainyl quite possible that all they've ever been tested with have
always started tag allocation from zero, so while the "start at an offset"
thing is fairly clever for other reasons, it probably was the wrong thing
to do.
Maybe we can just have something count "outstanding async/sync requests".
Linus
next prev parent reply other threads:[~2008-11-10 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 5:19 Tejun Heo
2008-11-10 5:30 ` Tejun Heo
2008-11-10 5:48 ` [PATCH] libata: revert convert-to-block-tagging patches Tejun Heo
2008-11-10 12:05 ` request to revert libata-convert-to-block-tagging patches Jens Axboe
2008-11-10 12:09 ` Jens Axboe
2008-11-10 16:00 ` Linus Torvalds
2008-11-10 17:10 ` Jens Axboe
2008-11-10 13:24 ` Tejun Heo
2008-11-10 16:03 ` Linus Torvalds [this message]
2008-11-10 22:55 ` Jeff Garzik
2008-11-12 1:11 ` Linus Torvalds
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=alpine.LFD.2.00.0811100800420.3468@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®