All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Leon Woestenberg <leon.woestenberg@gmail.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:32:05 +0200	[thread overview]
Message-ID: <20081002163205.GJ19428@kernel.dk> (raw)
In-Reply-To: <c384c5ea0810020915r3023bapecc99b7fcd67b81c@mail.gmail.com>

On Thu, Oct 02 2008, Leon Woestenberg wrote:
> 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?

Download:

http://brick.kernel.dk/snaps/splice-git-latest.tar.gz

which has lots of little examples for splice. You would want to do
something ala

# splice-in /dev/my-pci-device | splice-out /dev/sda

in one app of course, but take a look at the examples and get a feel for
the interface...

BTW, in my splice branch I have this queued as well. Not going anywhere
for now, but should get updated and tested every now and then.

http://git.kernel.dk/?p=linux-2.6-block.git;a=shortlog;h=refs/heads/splice

-- 
Jens Axboe


      reply	other threads:[~2008-10-02 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26  7:29 disk IO directly from PCI memory to block device sectors 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
2008-10-02 16:32             ` Jens Axboe [this message]

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=20081002163205.GJ19428@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=Martin.Leisner@xerox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=leon.woestenberg@gmail.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 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.