linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/5] xfs: speed up large directory modifications
Date: Thu, 25 Oct 2018 09:57:11 +1100	[thread overview]
Message-ID: <20181024225716.19459-1-david@fromorbit.com> (raw)

Hi folks,

I've finally  had time to clean this series up properly and get it
tested. This makes growing large directories much faster by avoiding
unnecessray processing during free space searches. Befor making
those changes, I factored the code to make it much cleaner and more
obvious what the different bits of the algorithms are doing.
hopefully that makes the optimisations easier to understand as their
scope is now much clearer. Performance numbers are in the patches
that add the optimisations.

These have been in my test trees for the past month, so they seem
fairly solid at this point. These are for the next dev cycle, not
the one that is being merged right now, though.

Cheers,

Dave.

             reply	other threads:[~2018-10-25  7:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 22:57 Dave Chinner [this message]
2018-10-24 22:57 ` [PATCH 1/5] xfs: move xfs_dir2_addname() Dave Chinner
2018-10-26  9:24   ` Christoph Hellwig
2018-10-24 22:57 ` [PATCH 2/5] xfs: factor data block addition from xfs_dir2_node_addname_int() Dave Chinner
2018-10-26  9:45   ` Christoph Hellwig
2018-10-26 10:52     ` Dave Chinner
2018-10-26 12:01       ` Christoph Hellwig
2018-10-24 22:57 ` [PATCH 3/5] xfs: factor free block index lookup " Dave Chinner
2018-10-26  9:48   ` Christoph Hellwig
2018-10-26 10:49     ` Dave Chinner
2018-10-24 22:57 ` [PATCH 4/5] xfs: speed up directory bestfree block scanning Dave Chinner
2018-10-26 10:24   ` Christoph Hellwig
2018-10-26 10:58     ` Dave Chinner
2018-10-26 11:56       ` Christoph Hellwig
2018-10-26 12:12         ` Christoph Hellwig
2018-10-24 22:57 ` [PATCH 5/5] xfs: reverse search directory freespace indexes Dave Chinner
2018-10-26 12:14   ` 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=20181024225716.19459-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 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).