From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Jens Axboe" <jens.axboe@oracle.com>
Cc: "Leisner, Martin" <Martin.Leisner@xerox.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
marty <martyleisner@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: disk IO directly from PCI memory to block device sectors
Date: Thu, 2 Oct 2008 18:15:18 +0200 [thread overview]
Message-ID: <c384c5ea0810020915r3023bapecc99b7fcd67b81c@mail.gmail.com> (raw)
In-Reply-To: <20081001190546.GQ19428@kernel.dk>
Hello Jens,
On Wed, Oct 1, 2008 at 9:05 PM, Jens Axboe <jens.axboe@oracle.com> wrote:
> On Mon, Sep 29 2008, Jens Axboe wrote:
>> On Fri, Sep 26 2008, Leisner, Martin wrote:
>> IMHO, this interface totally rocks. It's really async like splice was
>
> Alright, so this one actually works :-)
> Apart from fixing the bugs in it, it's also more clever in using the bio
> for the write part. It'll reuse the same bio in the splice actor until
> it's full, only then submitting it and allocating a new one. The read
> part works the same way.
>
I have been following this thread trying to grasp a very nifty use
case (high speed acquisition and storage of data) of splice.
I think it would make a perfect example of splice functionality.
What would the user space part look like to exercise this interface?
And whoever writes Linux Device Drivers 4th edition or one of the
kernel books; make sure this topic in is :-)
Regards,
--
Leon
next prev parent reply other threads:[~2008-10-02 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 7:29 marty
2008-09-26 8:03 ` Jens Axboe
2008-09-26 8:46 ` Alan Cox
2008-09-26 9:11 ` Jens Axboe
2008-09-26 10:06 ` Alan Cox
2008-09-26 10:19 ` Jens Axboe
2008-09-26 11:34 ` Jens Axboe
2008-09-26 15:51 ` Leisner, Martin
2008-09-29 13:02 ` Jens Axboe
2008-10-01 19:05 ` Jens Axboe
2008-10-02 16:15 ` Leon Woestenberg [this message]
2008-10-02 16:32 ` Jens Axboe
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=c384c5ea0810020915r3023bapecc99b7fcd67b81c@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=Martin.Leisner@xerox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martyleisner@yahoo.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
all inboxes | Powered by JetHome®