public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: wcheng@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/gfs-kernel/src/gfs ops_file.c Date: Sat, 13 May 2006 02:51:00 -0000 [thread overview] Message-ID: <20060513025132.6976.qmail@sourceware.org> (raw) CVSROOT: /cvs/cluster Module name: cluster Branch: RHEL4 Changes by: wcheng@sourceware.org 2006-05-13 02:51:32 Modified files: gfs-kernel/src/gfs: ops_file.c Log message: Found a performance issue in gfs_fsync() implementation where GL_SYNC glock flag introduces repeated page writes and meta data flushes via customer benchmark. The upload patch: 1. Replace the shared lock with an exclusive lock. 2. Borrow linux VFS layer's generic_osync_inode() (used by O_SYNC code path) to flush the local in-core inode into the disk, instead of the original GFS inode_go_sync(). After the changes, the (application) bandwidth jumps from 240.94 KB/s to 2.67 MB/s, very close (and almost equal) to ext3's under lock_nolock mount option. For other details, check out bugzilla 190950. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_file.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.16.2.9&r2=1.16.2.10
next reply other threads:[~2006-05-13 2:51 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-13 2:51 wcheng [this message] -- strict thread matches above, loose matches on Subject: below -- 2008-01-30 9:05 fabbione 2008-01-28 6:36 fabbione 2007-06-17 3:35 wcheng 2007-06-17 2:56 wcheng 2007-05-24 22:34 wcheng 2007-05-04 14:49 wcheng 2007-01-17 22:30 wcheng 2006-11-17 20:39 wcheng 2006-11-17 20:33 wcheng 2006-11-17 20:26 wcheng 2006-11-17 19:49 wcheng 2006-11-17 16:15 wcheng 2006-11-17 5:00 wcheng 2006-10-27 16:22 wcheng 2006-10-24 3:35 wcheng 2006-06-07 14:06 wcheng 2006-06-02 4:56 wcheng 2006-05-31 18:29 wcheng 2006-05-23 22:28 wcheng 2006-02-13 20:28 cfeist 2006-01-05 17:18 teigland 2005-12-10 0:48 bmarzins 2005-12-10 0:47 bmarzins 2005-12-10 0:44 bmarzins 2005-12-10 0:44 bmarzins 2005-11-21 16:51 teigland 2005-11-21 16:49 teigland 2005-11-21 16:41 teigland 2005-11-17 20:21 wcheng 2005-11-14 22:52 wcheng 2005-11-01 19:23 wcheng
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=20060513025132.6976.qmail@sourceware.org \ --to=wcheng@sourceware.org \ --cc=cluster-cvs@sources.redhat.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).