Hi all,
we are currently developing (as part of my dissertation)
a research-platform to study some new ideas in
constructing transport systems to support applications
with realtime-requirements (e.g. multimedia) and new
networking technologies. The test-platform consists of
typical multimedia-elements, such as sources, filters,
sinks and transport-modules, which can be distributed
across a set of computers.
To achieve the principle of sparing ressource-usage - which
we consider fundamental for multimedia-systems - we are
looking for new (already implemented or planned) mechanisms to
avoid copying the data-streams where possible (Device-IO,
especially Network-IO; User-User-IPC).
That's why i'd like to ask if one of the net-core developers
could give us a (more or less - depends on what you've
documented so far) detailed description of the newly
implemented zero-copy mechanisms in the network-stack.
We are interested in how to use it (changed network-API?)
and also in the internal architecture.
We already had a look at the kernel mailingslist
archieves and some search machines, but all we found
were some fragments of the puzzle only. Before digging into
the sourcecode we try this way to get an overall description.
Our second question: Are there any plans for contructing
a general copy-avoidance infrastructure (smth. like UVM in
NetBSD does) and new IPC-mechanisms on top of it yet??
Thanks in advance.
Alexander Eichhorn
--
Alexander Eichhorn
Technical University of Ilmenau
Computer Science And Automation Faculty
Distributed Systems and Operating Systems Department
Phone +49 3677 69 4557, Fax +49 3677 69 4541
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
