linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: torn5 <torn5@shiftmail.org>
Cc: Josef Bacik <josef@redhat.com>,
	Jon Leighton <j@jonathanleighton.com>,
	linux-ext4@vger.kernel.org
Subject: Re: Severe slowdown caused by jbd2 process
Date: Mon, 24 Jan 2011 15:16:03 -0500	[thread overview]
Message-ID: <20110124201603.GA5131@thunk.org> (raw)
In-Reply-To: <4D3C76BE.3090908@shiftmail.org>

On Sun, Jan 23, 2011 at 07:43:10PM +0100, torn5 wrote:
> I thought it was possible via the completion notifications from the disk.
> AFAIK if a disk is in NCQ mode it will return completion for a
> command only when the write was really delivered to the platters.
> While in non-NCQ mode the disk immediately returns completion and
> caches the write. Is this correct?

No, that's not correct.  The completion notification from the disk is
merely that the DMA has completed.  It does not mean that the data has
hit the platters.  This is true in both NCQ and non-NCQ mode.

You can disable the write cache (which is what I think you're thinking
about), but the performance hit is pretty significant on standard
HDD's.

						- Ted

  reply	other threads:[~2011-01-24 20:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  0:13 Severe slowdown caused by jbd2 process Jon Leighton
2011-01-21  1:31 ` Josef Bacik
     [not found]   ` <1295601083.5799.3.camel@tybalt>
2011-01-21 12:59     ` Josef Bacik
2011-01-21 14:03       ` Josef Bacik
2011-01-21 14:28         ` Jon Leighton
2011-01-21 14:31           ` Josef Bacik
2011-01-21 23:56             ` Ted Ts'o
2011-01-22  1:11               ` torn5
2011-01-22  1:34                 ` Ted Ts'o
2011-01-22 16:21                   ` torn5
2011-01-22 19:37                     ` Theodore Tso
2011-01-22 23:22                       ` torn5
2011-01-23  5:17                         ` Ted Ts'o
2011-01-23 18:43                           ` torn5
2011-01-24 20:16                             ` Ted Ts'o [this message]
2011-01-22 13:05               ` Ric Wheeler
2011-01-24 20:41             ` Darrick J. Wong

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=20110124201603.GA5131@thunk.org \
    --to=tytso@mit.edu \
    --cc=j@jonathanleighton.com \
    --cc=josef@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=torn5@shiftmail.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).