All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Abhijit Paithankar <apaithan@akamai.com>
Cc: linux-fsdevel@vger.kernel.org, Andreas Dilger <adilger@sun.com>
Subject: Re: [RFC PATCH] Filesystem Journal Notifications
Date: Mon, 15 Sep 2008 14:23:57 +0100	[thread overview]
Message-ID: <20080915132357.GA10973@shareable.org> (raw)
In-Reply-To: <20080912220649.GB26999@apaithan-desktop.sanmateo.corp.akamai.com>

Abhijit Paithankar wrote:
> One way to do it is to fsync every few operations. However, fsync is
> blocking and affects performance.
>
> The other (more efficient) way is to have the filesystem notify the
> application when a transaction/change is written to disk.

Is this more efficient than aio_fsync, and if so, why?

For file writes, aio_fsync seems like a cleaner interface, and if
that's not fast enough, it could be made faster - perhaps using code
form this patch.  (An aio_fsync_ranges would be even better).

-- Jamie

  parent reply	other threads:[~2008-09-15 13:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 22:06 [RFC PATCH] Filesystem Journal Notifications Abhijit Paithankar
2008-09-13  9:19 ` Dave Chinner
2008-09-15  2:31 ` Andreas Dilger
2008-09-15  5:39   ` Andreas Dilger
2008-09-15 19:36     ` Abhijit Paithankar
2008-09-15 23:37       ` Andreas Dilger
2008-09-16 23:05         ` Abhijit Paithankar
2008-09-19 20:34           ` Andreas Dilger
2008-09-20 15:51             ` Jamie Lokier
2008-09-20  5:15       ` Jan Kara
2008-09-23 22:26         ` Andreas Dilger
2008-09-15 13:23 ` Jamie Lokier [this message]
2008-09-17  0:06   ` Abhijit Paithankar
2008-09-17 11:35     ` Jamie Lokier

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=20080915132357.GA10973@shareable.org \
    --to=jamie@shareable.org \
    --cc=adilger@sun.com \
    --cc=apaithan@akamai.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /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.