From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>,
Chuck Lever <chuck.lever@oracle.com>,
"lsf-pc\@lists.linux-foundation.org"
<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" <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:22:49 -0500 [thread overview]
Message-ID: <yq1ty3cvcee.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <DE0353DF-83EA-480E-9C42-1EE760D6EE41@dilger.ca> (Andreas Dilger's message of "Thu, 26 Jan 2012 09:34:44 -0700")
>>>>> "Andreas" == Andreas Dilger <adilger@dilger.ca> writes:
Andreas> Is there a description of sys_dio() somewhere?
This was the original draft:
http://www.spinics.net/lists/linux-mm/msg14512.html
Andreas> In particular, I'm interested to know whether it allows full
Andreas> scatter-gather IO submission, unlike pwrite() which only allows
Andreas> multiple input buffers, and not multiple file offsets.
Each request descriptor contains buffer, target file, and offset. So
it's a single entry per descriptor. But many descriptors can be
submitted (and reaped) in a single syscall. So you don't have the single
file offset limitation of pwritev().
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2012-01-31 2:23 UTC|newest]
Thread overview: 25+ 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-26 12:31 ` Bernd Schubert
2012-01-26 14:53 ` Martin K. Petersen
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:21 ` Chuck Lever
2012-01-31 20:04 ` Martin K. Petersen
2012-01-31 2:10 ` Martin K. Petersen
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: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 22:52 ` Bernd Schubert
2012-02-01 18:15 ` Martin K. Petersen
2012-02-01 23:03 ` Boaz Harrosh
[not found] ` <DE0353DF-83EA-480E-9C42-1EE760D6EE41@dilger.ca>
2012-01-31 2:22 ` Martin K. Petersen [this message]
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=yq1ty3cvcee.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=adilger@dilger.ca \
--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 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).