From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange performance change 59 -> 61/62
Date: Fri, 21 Feb 2003 12:20:24 -0800 [thread overview]
Message-ID: <20030221122024.040055a0.akpm@digeo.com> (raw)
In-Reply-To: <11870000.1045848448@[10.10.2.4]>
"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> >> Some more stats ... which look rather suspicious. 600% increase for
> >> dentry_open and __mark_inode_dirty? Hmmmmm.
> >
> > __mark_inode_dirty() just got itself an smp_mb(). Would be instructive to
> > disable that.
> >
> > dentry_open(): don't know - fs/open.c hasn't changed at all. Perhaps
> > dcache_rcu has caused additional pingpong?
>
> 2.5.59-mjb6 84 __mark_inode_dirty
> 2.5.61-mjb1 594 __mark_inode_dirty
> 2.5.61-mjb1-no_mb 74 __mark_inode_dirty
>
> Yup, that fixed that one ... but presumably it was put there for a reason,
> so I can't just rip it out ;-) Thanks, I'll go take a closer look at the
> others.
mark_inode_dirty() tends to be called _very_ frequently. Too frequently.
Could you try remounting all filesystems noatime with
mount /mnt/point -o remount,noatime
and the below patch will prevent us calling the barrier-happy
current_kernel_time() for noatime mounts.
diff -puN fs/inode.c~update_atime-speedup fs/inode.c
--- 25/fs/inode.c~update_atime-speedup Fri Feb 21 12:17:00 2003
+++ 25-akpm/fs/inode.c Fri Feb 21 12:17:33 2003
@@ -1091,17 +1091,20 @@ sector_t bmap(struct inode * inode, sect
void update_atime(struct inode *inode)
{
- struct timespec now = CURRENT_TIME;
+ struct timespec now;
- /* Can later do this more lazily with a per superblock interval */
- if (timespec_equal(&inode->i_atime, &now))
- return;
if (IS_NOATIME(inode))
return;
if (IS_NODIRATIME(inode) && S_ISDIR(inode->i_mode))
return;
if (IS_RDONLY(inode))
return;
+
+ now = CURRENT_TIME;
+
+ /* Can later do this more lazily with a per superblock interval */
+ if (timespec_equal(&inode->i_atime, &now))
+ return;
inode->i_atime = now;
mark_inode_dirty_sync(inode);
}
_
next prev parent reply other threads:[~2003-02-21 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 16:23 Martin J. Bligh
2003-02-19 18:19 ` Andrew Morton
2003-02-21 7:19 ` Martin J. Bligh
2003-02-21 7:28 ` Martin J. Bligh
2003-02-21 7:45 ` Andrew Morton
2003-02-21 17:27 ` Martin J. Bligh
2003-02-21 20:20 ` Andrew Morton [this message]
2003-02-22 7:46 ` Martin J. Bligh
2003-02-22 8:04 ` Andrew Morton
2003-02-22 8:10 ` Martin J. Bligh
2003-02-19 17:19 Martin J. Bligh
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=20030221122024.040055a0.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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
all inboxes | Powered by JetHome®