From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [Patch] how about remove the sync in ocfs_file_open?
Date: Mon Aug 2 15:11:51 2004 [thread overview]
Message-ID: <20040802200334.GH8008@ca-server1.us.oracle.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8404FFE3CD@pdsmsx403>
On Thu, Jul 29, 2004 at 02:19:57AM +0800, Ling, Xiaofeng wrote:
> >From the data below, this sync cause the performance of writting from
> second time downgrade(13M compare to 544M for 128K file).
> and the sync has no use here.
Well, since it's really easy to revert, we're going to try this one and see
if it breaks anything multi-node. If it does, you can be sure we'll put the
sync_inode back :)
--Mark
> Index: file.c
> ===================================================================
> --- file.c (revision 1308)
> +++ file.c (working copy)
> @@ -300,7 +301,6 @@
> have_oin_sem = 0;
> }
>
> - status = ocfs_sync_inode(inode);
>
> leave:
> if (have_oin_sem) {
>
>
> before remove
> -----------------------------------------------------------------
> ./ben -0 -p10 -a
> create file /ocfs/ocfs_test25032 of size 128K successfully
> total:128.000K Time:0.562 Rate:227758KB
> total:128.000K Time:9.795 Rate:13068KB
> total:128.000K Time:9.687 Rate:13214KB
> total:128.000K Time:8.999 Rate:14224KB
> total:128.000K Time:9.817 Rate:13039KB
> total:128.000K Time:9.802 Rate:13059KB
> total:128.000K Time:9.146 Rate:13995KB
> total:128.000K Time:9.646 Rate:13270KB
> total:128.000K Time:9.655 Rate:13257KB
> total:128.000K Time:9.028 Rate:14178KB
> total:1280.000K Time:87.329 Rate:14657KB
>
> after remove
> ------------------------------------------------------------------------
> ------------------
> ./ben -0 -p10 -a
> create file /ocfs/ocfs_test24613 of size 128K successfully
> total:128.000K Time:0.292 Rate:438356KB
> total:128.000K Time:0.235 Rate:544681KB
> total:128.000K Time:0.209 Rate:612440KB
> total:128.000K Time:0.225 Rate:568889KB
> total:128.000K Time:0.207 Rate:618357KB
> total:128.000K Time:0.219 Rate:584475KB
> total:128.000K Time:0.205 Rate:624390KB
> total:128.000K Time:0.207 Rate:618357KB
> total:128.000K Time:0.204 Rate:627451KB
> total:128.000K Time:0.204 Rate:627451KB
> total:1280.000K Time:3.083 Rate:415180KB
> -------------------
>
>
> Index: file.c
> ===================================================================
> --- file.c (revision 1308)
> +++ file.c (working copy)
> @@ -300,7 +301,6 @@
> have_oin_sem = 0;
> }
>
> - status = ocfs_sync_inode(inode);
>
> leave:
> if (have_oin_sem) {
>
>
>
>
> Intel China Software Lab.
> iNet: 8-752-1243
> 021-52574545-1243(O)
> xfling@users.sourceforge.net
> Opinions are my own and don't represent those of my employer
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel@oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
prev parent reply other threads:[~2004-08-02 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 13:20 [Ocfs2-devel] [Patch] how about remove the sync in ocfs_file_open? Ling, Xiaofeng
2004-08-02 15:11 ` Mark Fasheh [this message]
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=20040802200334.GH8008@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.