From: Jan Kara <jack@suse.cz>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, Andreas Dilger <adilger@dilger.ca>,
Shuichi Ihara <sihara@ddn.com>, Wang Shilong <wshilong@ddn.com>
Subject: Re: [PATCH 0/27 v2] Quota scalability patches
Date: Thu, 31 Aug 2017 11:48:18 +0200 [thread overview]
Message-ID: <20170831094818.GA9783@quack2.suse.cz> (raw)
In-Reply-To: <CAP9B-QntdC06C8fAinqU6-4V6SzC_k4SyEpgHAqZ5zEF7ERq-w@mail.gmail.com>
On Thu 31-08-17 17:09:26, Wang Shilong wrote:
> This is without your patch:
>
> no Quota � � �quota � � quota,project � ��
> 1 �851,207 � � 341,941 � 178,686 � ��
> 2 �850,368 � � 342,233 � 191,755 � ��
> 3 �848,877 � � 342,768 � �193,807
>
> With your patchset:
> no quota � � �quota � � �quota,project
> 1 �853,391 � 448,378 �385,292�
> 2 �851,379 � 448,375 �407,716 ��
> 3 �850,203 � 448,415 �406,813 ��
>
> We still see creation regression here, but your patchset help a lot.
OK, still quite some way to go... There will always be some cost associated
with quota bookkeeping especially since this has to be synchronized across
CPUs to allow for reliable limits checking. But 50% seems quite a bit.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-08-31 9:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 11:54 [PATCH 0/27 v2] Quota scalability patches Jan Kara
2017-08-21 11:54 ` [PATCH 01/27] quota: Convert dqio_mutex to rwsem Jan Kara
2017-08-21 11:54 ` [PATCH 02/27] quota: Do more fine-grained locking in dquot_acquire() Jan Kara
2017-08-21 11:54 ` [PATCH 03/27] quota: Acquire dqio_sem for reading in dquot_get_next_id() Jan Kara
2017-08-21 11:54 ` [PATCH 04/27] quota: Acquire dqio_sem for reading in vfs_load_quota_inode() Jan Kara
2017-08-21 11:54 ` [PATCH 05/27] quota: Protect dquot writeout with dq_lock Jan Kara
2017-08-21 11:54 ` [PATCH 06/27] quota: Push dqio_sem down to ->read_dqblk() Jan Kara
2017-08-21 11:54 ` [PATCH 07/27] quota: Remove locking for reading from the old quota format Jan Kara
2017-08-21 11:54 ` [PATCH 08/27] quota: Push dqio_sem down to ->write_dqblk() Jan Kara
2017-08-21 11:54 ` [PATCH 09/27] quota: Do not acquire dqio_sem for dquot overwrites in v2 format Jan Kara
2017-08-21 11:55 ` [PATCH 10/27] quota: Remove locking for writing to the old quota format Jan Kara
2017-08-21 11:55 ` [PATCH 11/27] quota: Push dqio_sem down to ->release_dqblk() Jan Kara
2017-08-21 11:55 ` [PATCH 12/27] quota: Push dqio_sem down to ->get_next_id() Jan Kara
2017-08-21 11:55 ` [PATCH 13/27] quota: Push dqio_sem down to ->write_file_info() Jan Kara
2017-08-21 11:55 ` [PATCH 14/27] quota: Push dqio_sem down to ->read_file_info() Jan Kara
2017-08-21 11:55 ` [PATCH 15/27] quota: Fix error codes in v2_read_file_info() Jan Kara
2017-08-21 11:55 ` [PATCH 16/27] quota: Propagate ->quota_read errors from v2_read_file_info() Jan Kara
2017-08-21 11:55 ` [PATCH 17/27] quota: Fix possible corruption of dqi_flags Jan Kara
2017-08-21 11:55 ` [PATCH 18/27] quota: Do not dirty bad dquots Jan Kara
2017-08-21 11:55 ` [PATCH 19/27] quota: Move locking into clear_dquot_dirty() Jan Kara
2017-08-21 11:55 ` [PATCH 20/27] quota: Remove dq_wait_unused from dquot Jan Kara
2017-08-21 11:55 ` [PATCH 21/27] quota: Allow disabling tracking of dirty dquots in a list Jan Kara
2017-08-21 11:55 ` [PATCH 22/27] ext4: Disable dirty list tracking of dquots when journalling quotas Jan Kara
2017-08-21 11:55 ` [PATCH 23/27] quota: Inline functions into their callsites Jan Kara
2017-08-21 11:55 ` [PATCH 24/27] quota: Inline inode_{incr,decr}_space() into callsites Jan Kara
2017-08-21 11:55 ` [PATCH 25/27] quota: Inline dquot_[re]claim_reserved_space() into callsite Jan Kara
2017-08-21 11:55 ` [PATCH 26/27] fs: Provide __inode_get_bytes() Jan Kara
2017-08-21 11:55 ` [PATCH 27/27] quota: Reduce contention on dq_data_lock Jan Kara
[not found] ` <CAP9B-Qnnh3V9kq1qHemWD5s7DmA3Ef3LAVvgzLrbb7pgLEqb8w@mail.gmail.com>
2017-08-31 8:28 ` [PATCH 0/27 v2] Quota scalability patches Jan Kara
[not found] ` <CAP9B-QntdC06C8fAinqU6-4V6SzC_k4SyEpgHAqZ5zEF7ERq-w@mail.gmail.com>
2017-08-31 9:48 ` Jan Kara [this message]
[not found] ` <CAP9B-Qn1VvfnDZNH4eM1rWxenO6M=KJ+mSurEuc2FC70YwWoyQ@mail.gmail.com>
2017-08-31 12:22 ` Jan Kara
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=20170831094818.GA9783@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adilger@dilger.ca \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sihara@ddn.com \
--cc=wangshilong1991@gmail.com \
--cc=wshilong@ddn.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).