From: Leon Woestenberg <leon.woestenberg@gmail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Steve Rottinger <steve@pentek.com>, linux-kernel@vger.kernel.org
Subject: Re: splice methods in character device driver
Date: Sat, 13 Jun 2009 00:05:09 +0200 [thread overview]
Message-ID: <c384c5ea0906121505g7ab137dp3bbc202da0d43bcd@mail.gmail.com> (raw)
In-Reply-To: <20090608070503.GB11363@kernel.dk>
Hello Jens,
On Mon, Jun 8, 2009 at 9:05 AM, Jens Axboe<jens.axboe@oracle.com> wrote:
> On Sat, Jun 06 2009, Leon Woestenberg wrote:
>> How can I pass information from the splice_read(), which spawns a hardware
>> DMA to the pages in my case, to the confirm() hook which is called at some
>> (random) time in the future?
>
> There's a ->private for each pipe_buffer, so you can pass along info on
> a per-page granularity.
>
So, this means in my driver's splice_read(), I must set
pipe->bufs[i]->private for each 0 <= i < PIPE_BUFFERS?
struct pipe_buffer {
...
unsigned long private;
};
struct pipe_inode_info {
...
struct pipe_buffer bufs[PIPE_BUFFERS];
};
static int splice_read(..., struct pipe_inode_info *pipe, ...)
Regards,
--
Leon
next prev parent reply other threads:[~2009-06-12 22:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 14:40 Steve Rottinger
2009-05-11 19:22 ` Jens Axboe
2009-05-13 16:59 ` Steve Rottinger
2009-06-03 21:32 ` Leon Woestenberg
2009-06-04 7:32 ` Jens Axboe
2009-06-04 13:20 ` Steve Rottinger
2009-06-12 19:21 ` Leon Woestenberg
2009-06-12 19:59 ` Jens Axboe
2009-06-12 20:45 ` Steve Rottinger
2009-06-16 11:59 ` Jens Axboe
2009-06-16 15:06 ` Steve Rottinger
2009-06-16 18:24 ` [RFC][PATCH] add support for shrinking/growing a pipe (Was "Re: splice methods in character device driver") Jens Axboe
2009-06-16 18:28 ` splice methods in character device driver Jens Axboe
2009-06-06 21:25 ` Leon Woestenberg
2009-06-08 7:05 ` Jens Axboe
2009-06-12 22:05 ` Leon Woestenberg [this message]
2009-06-13 7:26 ` Jens Axboe
2009-06-13 20:04 ` Leon Woestenberg
2009-06-16 11:57 ` 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=c384c5ea0906121505g7ab137dp3bbc202da0d43bcd@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@pentek.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
Powered by JetHome