From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Chuck Lever <chuck.lever@oracle.com>,
lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-scsi@vger.kernel.org,
Sven Breuner <sven.breuner@itwm.fraunhofer.de>
Subject: Re: [LSF/MM TOPIC] end-to-end data and metadata corruption detection
Date: Mon, 30 Jan 2012 21:10:31 -0500 [thread overview]
Message-ID: <yq1y5sovcyw.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <4F217F0C.6030105@itwm.fraunhofer.de> (Bernd Schubert's message of "Thu, 26 Jan 2012 17:27:56 +0100")
>>>>> "Bernd" == Bernd Schubert <bernd.schubert@itwm.fraunhofer.de> writes:
Bernd> Hmm, direct IO would mean we could not use the page cache. As we
Bernd> are using it, that would not really suit us. libaio then might be
Bernd> another option then.
Bernd> What kind of help do you exactly need?
As far as libaio is concerned I had a PoC working a few years ago. I'll
be happy to revive it if people are actually interested. So a real world
use case would be a great help...
But James is right that buffered I/O is much more challenging than
direct I/O. And all the use cases we have had have involved databases
and business apps that were doing direct I/O anyway.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2012-01-31 2:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 20:15 [LSF/MM TOPIC] end-to-end data and metadata corruption detection Chuck Lever
2012-01-17 20:15 ` Chuck Lever
2012-01-26 12:31 ` Bernd Schubert
2012-01-26 12:31 ` Bernd Schubert
2012-01-26 14:53 ` Martin K. Petersen
2012-01-26 14:53 ` Martin K. Petersen
2012-01-26 16:27 ` Bernd Schubert
2012-01-26 16:27 ` Bernd Schubert
2012-01-26 23:21 ` James Bottomley
2012-01-31 19:16 ` Bernd Schubert
2012-01-31 19:16 ` Bernd Schubert
2012-01-31 19:21 ` Chuck Lever
2012-01-31 20:04 ` Martin K. Petersen
2012-01-31 2:10 ` Martin K. Petersen [this message]
2012-01-31 19:22 ` Bernd Schubert
2012-01-31 19:28 ` Gregory Farnum
2012-02-01 16:45 ` [Lsf-pc] " Chris Mason
2012-02-01 16:52 ` James Bottomley
2012-02-01 17:41 ` Chris Mason
2012-02-01 17:41 ` Chris Mason
2012-02-01 17:59 ` Bernd Schubert
2012-02-01 18:16 ` James Bottomley
2012-02-01 18:30 ` Andrea Arcangeli
2012-02-02 9:04 ` Bernd Schubert
2012-02-02 19:26 ` Andrea Arcangeli
2012-02-02 19:46 ` Andreas Dilger
2012-02-02 19:46 ` Andreas Dilger
2012-02-02 22:52 ` Bernd Schubert
2012-02-02 22:52 ` Bernd Schubert
2012-02-01 18:15 ` Martin K. Petersen
2012-02-01 23:03 ` Boaz Harrosh
2012-02-01 23:03 ` Boaz Harrosh
2012-02-01 23:03 ` Boaz Harrosh
[not found] ` <DE0353DF-83EA-480E-9C42-1EE760D6EE41@dilger.ca>
2012-01-31 2:22 ` Martin K. Petersen
2012-01-31 2:22 ` Martin K. Petersen
2012-01-26 15:36 ` Martin K. Petersen
2012-01-26 15:36 ` Martin K. Petersen
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=yq1y5sovcyw.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=bernd.schubert@itwm.fraunhofer.de \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=sven.breuner@itwm.fraunhofer.de \
/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.