All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck readahead speedup performance report
Date: Fri, 8 Aug 2014 21:06:34 -0700	[thread overview]
Message-ID: <20140809040634.GL11191@birch.djwong.org> (raw)
In-Reply-To: <20140809035646.GA23604@thunk.org>

On Fri, Aug 08, 2014 at 11:56:46PM -0400, Theodore Ts'o wrote:
> Interesting results!
> 
> I noticed that the 1TB SSD did seem to suffer when you went from
> multi-threaded to single-threaded.  Was this a SATA-attached or
> USB-attached SSD?  And any insights about why the SSD seemed to
> require threading for better performance when using readaead?

PCIE, and it might simply be having issues. :/

One thing I haven't looked into is how exactly the kernel maps IO
requests to queue slots -- does each CPU get its own pile of slots to
use up?  I _think_ it does, but it's been a few months since I poked
at mq.  Hmm... max_sectors_kb=128, which isn't unusually odd.  Guess
I'll keep digging.

The other disks seems fairly normal, at least.

--D
> 
> 						- Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-08-09  4:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09  3:18 e2fsck readahead speedup performance report Darrick J. Wong
2014-08-09  3:22 ` Darrick J. Wong
2014-08-09  3:56 ` Theodore Ts'o
2014-08-09  4:06   ` Darrick J. Wong [this message]

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=20140809040634.GL11191@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.