From: Andrew Morton <akpm@zip.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [patch 6/19] mark_buffer_dirty() speedup
Date: Sun, 16 Jun 2002 23:51:50 -0700 [thread overview]
Message-ID: <3D0D8706.8B8CFA60@zip.com.au> (raw)
mark_buffer_dirty() is showing up on Anton's graphs. Avoiding the
buslocked RMW if the buffer is already dirty should fix that up.
--- 2.5.22/fs/buffer.c~mark_buffer_dirty-speedup Sun Jun 16 22:50:17 2002
+++ 2.5.22-akpm/fs/buffer.c Sun Jun 16 23:22:47 2002
@@ -1218,7 +1218,7 @@ void mark_buffer_dirty(struct buffer_hea
{
if (!buffer_uptodate(bh))
buffer_error();
- if (!test_set_buffer_dirty(bh))
+ if (!buffer_dirty(bh) && !test_set_buffer_dirty(bh))
__set_page_dirty_nobuffers(bh->b_page);
}
-
reply other threads:[~2002-06-17 6: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=3D0D8706.8B8CFA60@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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