From: Andrew Morton <akpm@osdl.org>
To: Sam Vilain <sam@vilain.net>
Cc: hirofumi@mail.parknet.co.jp, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Write the inode itself in block_fsync()
Date: Thu, 9 Mar 2006 20:10:53 -0800 [thread overview]
Message-ID: <20060309201053.682868db.akpm@osdl.org> (raw)
In-Reply-To: <4410D0F1.3030307@vilain.net>
Sam Vilain <sam@vilain.net> wrote:
>
> OGAWA Hirofumi wrote:
>
> >Hi,
> >
> >For block device's inode, we don't write a inode's meta data
> >itself. But, I think we should write inode's meta data for fsync().
> >
> >
>
> Ouch... won't that halve performance of database transaction logs?
Yes, it could well cause a lot more seeking to do atime and/or mtime
writes. Which aren't terribly important, really.
Unless I'm missing something, I suspect we'd be better off without this,
even though it's a correctness fix :(
next prev parent reply other threads:[~2006-03-10 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 16:22 [PATCH] Write the inode itself in block_fsync() OGAWA Hirofumi
2006-03-10 1:05 ` Sam Vilain
2006-03-10 4:10 ` Andrew Morton [this message]
2006-03-10 14:12 ` Bart Samwel
2006-03-10 15:18 ` OGAWA Hirofumi
2006-03-10 17:32 ` Bart Samwel
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=20060309201053.682868db.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@vilain.net \
/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