All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/3] xfs: miscellaneous improvements for 4.10
Date: Thu,  1 Dec 2016 21:30:49 +1100	[thread overview]
Message-ID: <20161201103052.28453-1-david@fromorbit.com> (raw)

Hi folks,

Some things that need review, hoepfully in time for the 4.10 cycle.
I've been running all these in my test kernels for some time now,
and they all seem stable and perform as expected. The btree stats
patch substantially reduces the icache footprint of the core btree
code. The rhashtable patch (many thanks to Lucas for writing the
original patch!) gets rid of most of the _xfs_buf_find() lookup
overhead. The CRC update optimisation patch (thanks to the
diagnosis, analysis and prototyping work done by Nick Piggin)
removes CRCs almost entirely from my kernel profiles on metadata
intensive workloads.

Comments, flames and thoughts welcome.

-Dave.


             reply	other threads:[~2016-12-01 10:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01 10:30 Dave Chinner [this message]
2016-12-01 10:30 ` [PATCH 1/3] xfs: make xfs btree stats less huge Dave Chinner
2016-12-02 13:20   ` Christoph Hellwig
2016-12-05  1:14     ` Dave Chinner
2016-12-05 12:48       ` Christoph Hellwig
2016-12-01 10:30 ` [PATCH 2/3] xfs: use rhashtable to track buffer cache Dave Chinner
2016-12-05 17:04   ` Christoph Hellwig
2016-12-07  6:32     ` Dave Chinner
2016-12-01 10:30 ` [PATCH 3/3] xfs: optimise CRC updates Dave Chinner
2016-12-02 13:22   ` Christoph Hellwig
2016-12-04 22:12     ` Dave Chinner
2016-12-05 12:48       ` Christoph Hellwig

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=20161201103052.28453-1-david@fromorbit.com \
    --to=david@fromorbit.com \
    --cc=linux-xfs@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 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.