From: Chris Smowton <cs448@cam.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Splice(): exports for module programmers
Date: Fri, 11 Jan 2008 02:43:49 +0000 [thread overview]
Message-ID: <4786D7E5.2080701@cam.ac.uk> (raw)
Just a couple of quick questions if anyone can shed light regarding
functions exported for modules relating to splice():
* Is there a particular reason why the useful helper __splice_from_pipe
is exported, but not the locking equivalent splice_from_pipe or its
equally useful helper splice_to_pipe?
* Similarly is there anything wrong with exporting the generic
pipe-buffer operations (e.g. generic_pipe_buf_map) to save effort
writing modules which implement splice_read and splice_write?
Are these unexported because they are unstable and not yet considered
suitable for use, or simply because nobody's written a module that
splice()s yet?
Chris
next reply other threads:[~2008-01-11 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 2:43 Chris Smowton [this message]
2008-01-11 9:06 ` Splice(): exports for module programmers 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=4786D7E5.2080701@cam.ac.uk \
--to=cs448@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
/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