From: Ted Ts'o <tytso@mit.edu>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>, linux-ext4@vger.kernel.org
Subject: Re: Query about DIO/AIO WRITE throttling and ext4 serialization
Date: Thu, 2 Jun 2011 21:11:29 -0400 [thread overview]
Message-ID: <20110603011129.GG16306@thunk.org> (raw)
In-Reply-To: <20110603005403.GB27129@redhat.com>
On Thu, Jun 02, 2011 at 08:54:03PM -0400, Vivek Goyal wrote:
>
> In this case I had done "sync" while aio-stress was doing O_DIRECT writes.
> I really don't have any real world example, I just cooked up a hypothetical
> scenario.
>
> Just wondering why ext4 and XFS behavior are different and which is a
> more appropriate behavior. ext4 does not seem to be waiting for all
> pending AIO/DIO to finish while XFS does.
I think this is something we can chalk up to "different
implementations do different things". I'm not convinced either
behviour is wrong per se. Granted, the recent work to make sync and
fsync not livelock in the face of continuing writes means that I'm
more happy with ext4's behaviour, but I don't think that means xfs's
behavior is wrong.
One of the things that I have thought about is sysctl which makes sync
a no-op unless you are root. The reason for that is that many system
administrators sometimes have a habit of typing sync, and on a heavily
loaded production server, this can really cause performance to go to
hell for up to tens of minutes. So it might make sense to not allow
non-root users from trashing overall system performance by running
sync....
- Ted
next prev parent reply other threads:[~2011-06-03 1:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 21:50 Query about DIO/AIO WRITE throttling and ext4 serialization Vivek Goyal
2011-06-02 1:22 ` Dave Chinner
2011-06-02 14:17 ` Vivek Goyal
2011-06-02 14:36 ` Vivek Goyal
2011-06-02 15:56 ` Vivek Goyal
2011-06-02 23:51 ` Dave Chinner
2011-06-03 0:27 ` Vivek Goyal
2011-06-03 0:43 ` Ted Ts'o
2011-06-03 0:54 ` Vivek Goyal
2011-06-03 1:02 ` Christoph Hellwig
2011-06-03 1:28 ` Vivek Goyal
2011-06-03 1:33 ` Vivek Goyal
2011-06-09 13:09 ` Christoph Hellwig
2011-06-03 3:30 ` Eric Sandeen
2011-06-03 5:00 ` Christoph Hellwig
2011-06-03 1:11 ` Ted Ts'o [this message]
2011-06-02 23:46 ` Dave Chinner
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=20110603011129.GG16306@thunk.org \
--to=tytso@mit.edu \
--cc=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=vgoyal@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: 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.