From: Tejun Heo <htejun@gmail.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
James.Smart@Emulex.Com,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Regarding ordered-tag support.
Date: Fri, 10 Feb 2006 09:45:16 +0900 [thread overview]
Message-ID: <43EBE21C.2020803@gmail.com> (raw)
In-Reply-To: <1139505635.3275.43.camel@mulgrave.il.steeleye.com>
Hello, James.
James Bottomley wrote:
>
> The fact that tasks can proceed in parallel, only the command components
> individual linked tasks must be serialised. so it supports the TCQ
> paradigm.
>
> Really, also, linked tasks is exactly what a JFS wants because most of
> the updates that would be linked are something like update log entry;
> modify metadata (or data); remove log entry.
>
I see your point, so it's not really a barrier anymore, but a sequence
of ordered writes with an intervening flush independent of other
unrelated writes. Some random thoughts...
* All writes in the ordered sequence will have to be done sequentially,
but unrelated writes are not affected. This can be overall gain.
* Can be implemented in block layer proper without using SCSI linked
task (probably with separate ->ordered_requests queue). What would be
the advantage of SCSI linked task?
* As it's finer grained than wholesale barrier, FS layer will need to
pay more attention.
Thanks for the explanation. :-)
--
tejun
next prev parent reply other threads:[~2006-02-10 0:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 6:40 Regarding ordered-tag support Tejun Heo
2006-02-08 15:49 ` James Bottomley
2006-02-08 16:10 ` Tejun
2006-02-08 16:25 ` James Smart
2006-02-08 16:57 ` Tejun
2006-02-08 17:07 ` James Bottomley
2006-02-08 17:18 ` Tejun
2006-02-08 17:27 ` James Bottomley
2006-02-08 18:04 ` Jeff Garzik
2006-02-09 4:12 ` Tejun Heo
2006-02-09 17:20 ` James Bottomley
2006-02-10 0:45 ` Tejun Heo [this message]
2006-02-08 16:26 ` James Bottomley
2006-02-08 16:22 ` James Smart
2006-02-08 20:50 ` James Bottomley
2006-02-08 20:59 ` James Bottomley
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=43EBE21C.2020803@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@SteelEye.com \
--cc=James.Smart@Emulex.Com \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@vger.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;
as well as URLs for NNTP newsgroup(s).