From: Jens Axboe <jens.axboe@oracle.com>
To: saeed bishara <saeed.bishara@gmail.com>
Cc: Tejun Heo <htejun@gmail.com>, Ric Wheeler <ric@emc.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/2] libata: turn off NCQ if queue depth is adjusted to 1
Date: Thu, 5 Oct 2006 11:08:22 +0200 [thread overview]
Message-ID: <20061005090820.GM5170@kernel.dk> (raw)
In-Reply-To: <20061004133755.GP7778@kernel.dk>
On Wed, Oct 04 2006, Jens Axboe wrote:
> On Wed, Oct 04 2006, saeed bishara wrote:
> > the NCQ commands contain the FUA (force unit access) field
> > (mandatory), so disabling the NCQ will waste this feature.
> > I don't know how much ans when this feature is usuable, but someday it
> > can be usefull.
>
> It's already useful, for io barriers. Yet another reason why the
> distinction between depth == 1 and NCQ needs to available.
Ehm, I completely missed the bigger picture - non-ncq has FUA available
too. So NCQ or not has no bearing on FUA functionality.
--
Jens Axboe
next prev parent reply other threads:[~2006-10-05 9:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 10:44 [PATCH 1/2] libata: cosmetic changes to constants Tejun Heo
2006-09-30 10:45 ` [PATCH 2/2] libata: turn off NCQ if queue depth is adjusted to 1 Tejun Heo
2006-09-30 18:04 ` Jens Axboe
2006-09-30 20:51 ` Alan Cox
2006-09-30 20:26 ` Jens Axboe
2006-10-01 0:17 ` Ric Wheeler
2006-10-01 0:29 ` Tejun Heo
2006-10-01 0:52 ` Ric Wheeler
2006-10-01 12:56 ` Ric Wheeler
2006-12-16 17:19 ` Jeff Garzik
2006-12-18 10:04 ` Jens Axboe
2006-10-01 19:55 ` Jens Axboe
2006-10-04 13:37 ` saeed bishara
2006-10-04 13:37 ` Jens Axboe
2006-10-05 9:08 ` Jens Axboe [this message]
2006-09-30 11:39 ` [PATCH 1/2] libata: cosmetic changes to constants Jeff Garzik
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=20061005090820.GM5170@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=ric@emc.com \
--cc=saeed.bishara@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.