new splicetee module

[oaitmous]

BPO	1545262
Nosy	@loewis
Files	splicetee.patch: patch v1

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2006-08-25.00:57:01.000>
created_at = <Date 2006-08-23.13:01:54.000>
labels = ['extension-modules']
title = 'new splicetee module'
updated_at = <Date 2006-08-25.00:57:01.000>
user = 'https://bugs.python.org/oaitmous'

bugs.python.org fields:

activity = <Date 2006-08-25.00:57:01.000>
actor = 'loewis'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2006-08-23.13:01:54.000>
creator = 'oaitmous'
dependencies = []
files = ['7496']
hgrepos = []
issue_num = 1545262
keywords = ['patch']
message_count = 2.0
messages = ['50978', '50979']
nosy_count = 2.0
nosy_names = ['loewis', 'oaitmous']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1545262'
versions = []

[oaitmous]

This module is an interface to the new splice()/tee()
system calls under Linux Kernel 2.6.17 and higher.
Splice allows one to transfer data from a stream to
another within the kernel, without need for user-land
involvement, while tee transfers data from a pipe to
another without consuming the data on the first pipe.
By combining both system calls, it is possible to
actually do zero-copy movement of data from one or many
sources to many destinations.
For more information about splice() and tee() system
call mechanisms :
http://kerneltrap.org/node/6505

We would like to know if this is worth for inclusion in
the standard Python distribution? What should be
modified to make it more "compliant" to the python
rules? This file will probably need to be updated to
conform to python style standards.

[loewis]

Logged In: YES
user_id=21627

See my comments to 1545275, packaging it up as a separate package on the
Cheeseshop should be the first step.

In the specific case, I think this should be added to posixmodule.c if it is
added at all. I don't think the system call should be done directly, but instead,
a C library interface should be used once available. Then, in turn, configure
should detect presence of the API.

Notice the documentation has bogus fragments of C.