From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: shaohua.li@intel.com, alex.shi@intel.com, jack@suse.cz
Subject: + dquot-do-full-inode-dirty-in-allocating-space.patch added to -mm tree
Date: Mon, 23 Aug 2010 13:52:18 -0700 [thread overview]
Message-ID: <201008232052.o7NKqI6c014187@imap1.linux-foundation.org> (raw)
The patch titled
dquot: do full inode dirty in allocating space
has been added to the -mm tree. Its filename is
dquot-do-full-inode-dirty-in-allocating-space.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: dquot: do full inode dirty in allocating space
From: Shaohua Li <shaohua.li@intel.com>
Alex Shi found a regression when doing ffsb test. The test has several
threads, and each thread creates a small file, write to it and then delete
it. ffsb reports about 20% regression and Alex bisected it to
43d2932d88e4 ("quota: Use mark_inode_dirty_sync instead of
mark_inode_dirty").
The test will call __mark_inode_dirty 3 times. Without this commit, we
only take inode_lock one time, while with it, we take the lock 3 times
with flags ( I_DIRTY_SYNC,I_DIRTY_PAGES,I_DIRTY). Perf shows the lock
contention increased too much. Below proposed patch fixes it.
fs is allocating blocks, which usually means file writes and the inode
will be dirtied soon. We fully dirty the inode to reduce some inode_lock
contention in several calls of __mark_inode_dirty.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
Signed-off-by: Alex Shi <alex.shi@intel.com>
Cc: Jan Kara <jack@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/quotaops.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN include/linux/quotaops.h~dquot-do-full-inode-dirty-in-allocating-space include/linux/quotaops.h
--- a/include/linux/quotaops.h~dquot-do-full-inode-dirty-in-allocating-space
+++ a/include/linux/quotaops.h
@@ -275,7 +275,7 @@ static inline int dquot_alloc_space(stru
ret = dquot_alloc_space_nodirty(inode, nr);
if (!ret)
- mark_inode_dirty_sync(inode);
+ mark_inode_dirty(inode);
return ret;
}
_
Patches currently in -mm which might be from shaohua.li@intel.com are
dquot-do-full-inode-dirty-in-allocating-space.patch
reply other threads:[~2010-08-23 20:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201008232052.o7NKqI6c014187@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=shaohua.li@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