From: Eric Sandeen <sandeen@redhat.com>
To: Niu Yawei <yawei.niu@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Cc: yawei.niu@intel.com, andreas.dilger@intel.com, jack@suse.cz,
lai.siyao@intel.com
Subject: Re: [PATCH] quota: remove dqptr_sem for scalability
Date: Fri, 23 May 2014 08:02:37 -0500 [thread overview]
Message-ID: <537F46ED.3050505@redhat.com> (raw)
In-Reply-To: <537EDB05.8030109@gmail.com>
On 5/23/14, 12:22 AM, Niu Yawei wrote:
> 于 2014/5/23 12:02, Eric Sandeen 写道:
>> On 5/22/14, 5:47 AM, Niu Yawei wrote:
>>> There are several global locks in the VFS quota code which hurts
>>> performance a lot when quota accounting enabled, dqptr_sem is the major one.
>>>
>>> This patch tries to make the VFS quota code scalable with minimal changes.
>>>
>>> Following tests (mdtest & dbench) were running over ext4 fs in a
>>> centos6.5 vm (8 cpus, 4G mem, kenrel: 3.15.0-rc5+), and the result shows
>>> the patch relieved the lock congestion a lot.
>>>
>> Just noticed this patch - FWIW, Lustre has a
>> "quota-replace-dqptr-sem-sles11sp2.patch" that they apply:
> Yes, I'm Lustre developer and trying to push the patch upstream. :)
I'm sorry. I took a quick glance at both and somehow didn't realize they
were the same. That's what I get for sending emails too late at night.
Sorry for the noise! Carry on... ;) And thanks for doing this!
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-23 13:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 10:47 [PATCH] quota: remove dqptr_sem for scalability Niu Yawei
2014-05-22 13:25 ` Jan Kara
2014-05-23 3:37 ` Niu Yawei
2014-05-27 10:13 ` [PATCH 2/3] quota: avoid unnecessary dqget()/dqput() calls Niu Yawei
2014-05-27 10:15 ` [PATCH 3/3] quota: remove dqptr_sem Niu Yawei
2014-05-23 4:02 ` [PATCH] quota: remove dqptr_sem for scalability Eric Sandeen
2014-05-23 5:22 ` Niu Yawei
2014-05-23 13:02 ` Eric Sandeen [this message]
2014-05-27 10:10 ` [PATCH 1/3] quota: protect Q_GETFMT by dqonoff_mutex Niu Yawei
2014-05-27 10:12 ` Christoph Hellwig
2014-05-27 10:28 ` Niu Yawei
2014-05-28 1:52 ` [PATCH 1/3 v2] " Niu Yawei
2014-06-02 7:32 ` Jan Kara
2014-05-28 1:53 ` [PATCH 2/3 v2] quota: avoid unnecessary dqget()/dqput() calls Niu Yawei
2014-06-02 7:42 ` Jan Kara
2014-05-28 1:55 ` [PATCH 3/3 v2] quota: remove dqptr_sem Niu Yawei
2014-05-28 2:01 ` Niu Yawei
2014-06-02 8:34 ` Jan Kara
2014-06-03 9:51 ` Niu Yawei
2014-06-03 15:43 ` Jan Kara
2014-06-04 4:19 ` [PATCH 1/5] quota: protect Q_GETFMT by dqonoff_mutex Niu Yawei
2014-06-04 15:36 ` Jan Kara
2014-06-04 4:20 ` [PATCH 2/5] quota: avoid unnecessary dqget()/dqput() calls Niu Yawei
2014-06-04 4:21 ` [PATCH 3/5] quota: simplify remove_inode_dquot_ref() Niu Yawei
2014-06-04 4:22 ` [PATCH 4/5] quota: missing lock in dqcache_shrink_scan() Niu Yawei
2014-06-04 4:23 ` [PATCH 5/5] quota: remove dqptr_sem Niu Yawei
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=537F46ED.3050505@redhat.com \
--to=sandeen@redhat.com \
--cc=andreas.dilger@intel.com \
--cc=jack@suse.cz \
--cc=lai.siyao@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=yawei.niu@gmail.com \
--cc=yawei.niu@intel.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 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).