linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Landman <joe.landman@gmail.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Steve Bergman <sbergman27@gmail.com>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Is this expected RAID10 performance?
Date: Sun, 09 Jun 2013 20:11:06 -0400	[thread overview]
Message-ID: <51B5199A.1050001@gmail.com> (raw)
In-Reply-To: <51B4F640.4030605@redhat.com>

On 06/09/2013 05:40 PM, Ric Wheeler wrote:
> On 06/09/2013 04:06 PM, Steve Bergman wrote:

[...]

>> a quick find/fgrep doesn't reveal any usage of fsync at all in any of
>> the ".py" files which ship with the distro. Perhaps the Python VM
>> invokes it automatically? Strace says no. And this is in an enterprise
>> distro which clearly states in its Administrator Manual sections on
>> Ext4 & XFS that you *must* use fsync to avoid losing data. I haven't
>> checked Ruby or Perl, but I think it's a pretty good guess that I'd
>> find the same thing.
>
> I don't know any details about Python, Ruby or Perl internals, but will
> poke around. Note that some of the standard libraries they call might
> also have buried calls in them to do the write thing with fsync() or
> fdatasync().

Perl's IO layer is tunable using various "personalities" you can invoke 
at module load, file open, on file descriptors, etc.  The syncs are in 
the standard library.  This said, a number of the distro Perl's are 
badly horribly broken (or out of date and EOLed for years now ... cough 
cough).  Python has similar capability, and its IO layer is usually a 
direct pass through to the underlying library calls.  You can force sync 
on IO, though most sane programmers won't do that.


  parent reply	other threads:[~2013-06-10  0:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08 19:56 Is this expected RAID10 performance? Steve Bergman
2013-06-09  3:08 ` Stan Hoeppner
2013-06-09 12:09 ` Ric Wheeler
2013-06-09 20:06   ` Steve Bergman
2013-06-09 21:40     ` Ric Wheeler
2013-06-09 23:08       ` Steve Bergman
2013-06-10  8:35         ` Stan Hoeppner
2013-06-10  0:11       ` Joe Landman [this message]
2013-06-09 22:05     ` Eric Sandeen
2013-06-09 23:34       ` Steve Bergman
2013-06-10  0:02         ` Eric Sandeen
2013-06-10  2:37           ` Steve Bergman
2013-06-10 10:00             ` Stan Hoeppner
2013-06-10  7:19           ` David Brown
2013-06-10  0:05     ` Joe Landman
  -- strict thread matches above, loose matches on Subject: below --
2013-06-09 23:53 Steve Bergman
2013-06-10  9:23 ` Stan Hoeppner
2013-06-06 23:52 Steve Bergman
2013-06-07  3:25 ` Stan Hoeppner
2013-06-07  7:51 ` Roger Heflin
2013-06-07  8:07   ` Alexander Zvyagin
2013-06-07 10:44     ` Steve Bergman
2013-06-07 10:52       ` Roman Mamedov
2013-06-07 11:25         ` Steve Bergman
2013-06-07 13:18           ` Stan Hoeppner
2013-06-07 13:54             ` Steve Bergman
2013-06-07 21:43               ` Bill Davidsen
2013-06-07 23:33               ` Stan Hoeppner
2013-06-07 12:39       ` Stan Hoeppner
2013-06-07 12:59         ` Steve Bergman
2013-06-07 20:51           ` Stan Hoeppner
2013-06-08 18:23 ` keld

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=51B5199A.1050001@gmail.com \
    --to=joe.landman@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rwheeler@redhat.com \
    --cc=sbergman27@gmail.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 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 NNTP newsgroup(s).