From: Dave Chinner <david@fromorbit.com>
To: Nathan Scott <nathans@redhat.com>
Cc: Mark Seger <mjseger@gmail.com>, xfs@oss.sgi.com
Subject: Re: definitions for /proc/fs/xfs/stat
Date: Mon, 17 Jun 2013 21:19:40 +1000 [thread overview]
Message-ID: <20130617111940.GM29338@dastard> (raw)
In-Reply-To: <1597962722.1767244.1371447710942.JavaMail.root@redhat.com>
On Mon, Jun 17, 2013 at 01:41:50AM -0400, Nathan Scott wrote:
> Hey Dave,
>
> ----- Original Message -----
> > ...
> > Must be an old version of RHEL6, because 6.4 doesn't do any IO at
> > all, same as upstream. This test workload is purely a metadata only
> > workload (no data is written) and so it all gets gathered up by
> > delayed logging.
>
> *nod* - RHEL6.3.
>
> > > I think it is still possible, FWIW. One could use python ctypes (as in
> > > Marks test program) and achieve a page-aligned POSIX memalign,
> >
> > I wasn't aware you could get memalign() through python at all. I
> > went looking for this exact solution a couple of month ago when
> > these problems started to be reported and couldn't find anything
> > ...
>
> Yes, on reflection it doesn't jive too well with the way python wants
> to do reads, in particular - os.read takes a file and a size, there's
> no buffer exposed at the API level (for input).
>
> It would need to be a separate python module to the core set I guess
> (with a C component), and a slightly different API - or at least some
> additional APIs which can take in an aligned buffer, rather than just
> allocating one each time - but I believe it's still feasible.
Oh, there were modules written to do this years ago. e.g this from
2006:
https://pypi.python.org/pypi/directio/1.0
There were even patches to provide a native interface in 2004, but
they got shot down, like all the future enhancement requests that
have happened since, mainly because the python maintainers don't
beleive that Direct IO is necessary.
I mean, Linus said Direct IO is for deranged monkeys, so nobody
should ever use direct IO, right? ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-17 11:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 16:37 definitions for /proc/fs/xfs/stat Mark Seger
2013-06-14 22:16 ` Nathan Scott
2013-06-14 22:37 ` Mark Seger
2013-06-15 0:17 ` Nathan Scott
2013-06-15 1:55 ` Mark Seger
2013-06-15 2:04 ` Dave Chinner
2013-06-15 10:35 ` Mark Seger
2013-06-15 16:22 ` Mark Seger
2013-06-16 0:11 ` Dave Chinner
2013-06-16 12:58 ` Mark Seger
2013-06-16 22:06 ` Dave Chinner
2013-06-16 22:31 ` Mark Seger
2013-06-16 23:14 ` Dave Chinner
2013-06-16 23:31 ` Mark Seger
2013-06-17 1:11 ` Nathan Scott
2013-06-17 2:46 ` Dave Chinner
2013-06-17 5:41 ` Nathan Scott
2013-06-17 10:57 ` Mark Seger
2013-06-17 11:13 ` Dave Chinner
2013-06-17 14:57 ` Mark Seger
2013-06-17 20:28 ` Stefan Ring
2013-06-18 0:15 ` Dave Chinner
2013-06-18 10:17 ` Mark Seger
2013-06-19 23:02 ` Useful stats (was Re: definitions for /proc/fs/xfs/stat) Nathan Scott
2013-06-17 11:19 ` Dave Chinner [this message]
2013-06-17 13:18 ` definitions for /proc/fs/xfs/stat Stan Hoeppner
2013-06-18 0:13 ` Mark Goodwin
2013-06-16 0:00 ` 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=20130617111940.GM29338@dastard \
--to=david@fromorbit.com \
--cc=mjseger@gmail.com \
--cc=nathans@redhat.com \
--cc=xfs@oss.sgi.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