All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org,
	Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@hp.com>
Subject: Re: [PATCH 0/2 v2] Improve orphan list scaling
Date: Mon, 19 May 2014 10:50:32 -0400	[thread overview]
Message-ID: <20140519145032.GA4012@thunk.org> (raw)
In-Reply-To: <1400185026-3972-1-git-send-email-jack@suse.cz>

On Thu, May 15, 2014 at 10:17:04PM +0200, Jan Kara wrote:
>   this is my version of patches to improve orphan list scaling by
> reducing amount of work done under global s_orphan_mutex. We are
> in disagreement with Thavatchai whose patches are better (see thread
> http://www.spinics.net/lists/linux-ext4/msg43220.html) so I guess it's
> up to Ted or other people on this list to decide.

I've started testing Jan's patches, mainly because of the simplicity
issue, and becase I agree with him that it's not clear that the hashed
mutexes is worth the extra complexity, even though it's a vanishingly
small number of systems that would show any benefit for them, and even
then it's not clear the changes are that much greater.

For the purposes of doing further optimizations, I'd prefer to start
with Jan's changes as a starting point and as a performance baseline
for further improvements.

If adding more mutexes or spinlocks, even 128 more mutexes per
filesystem, can be justified by a really huge improvement, it's
something that I won't completely rule out at this stage.  But I'd
rather avoid that unless the comparative benchmarks and lock_stat
reports make for an extremely convincing case.

Cheers,

					- Ted

      parent reply	other threads:[~2014-05-19 14:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 20:17 [PATCH 0/2 v2] Improve orphan list scaling Jan Kara
2014-05-15 20:17 ` [PATCH 1/2] ext4: Use sbi in ext4_orphan_{add|del}() Jan Kara
2014-05-15 20:17 ` [PATCH 2/2] ext4: Reduce contention on s_orphan_lock Jan Kara
2014-05-20  3:23   ` Theodore Ts'o
2014-05-20  8:33   ` Thavatchai Makphaibulchoke
2014-05-20  9:18     ` Jan Kara
2014-05-20 13:57     ` Theodore Ts'o
2014-05-20 17:16       ` Thavatchai Makphaibulchoke
2014-06-02 17:45       ` Thavatchai Makphaibulchoke
2014-06-03  8:52         ` Jan Kara
2014-06-16 19:20           ` Thavatchai Makphaibulchoke
2014-06-17  9:29             ` Jan Kara
2014-06-18  4:38               ` Thavatchai Makphaibulchoke
2014-06-18 10:37                 ` Jan Kara
2014-07-22  4:35                   ` Thavatchai Makphaibulchoke
2014-07-23  8:15                     ` Jan Kara
2014-05-19 14:50 ` Theodore Ts'o [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=20140519145032.GA4012@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=thavatchai.makpahibulchoke@hp.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.