ouroboros - Ouroboros main repository

	Commit message (Collapse)	Author	Age	Files	Lines
*	lib: Pass qosspec at flow allocation	Dimitri Staessens	2018-10-05	1	-51/+46
\| \| \| \| \| \| \| \| \| \| \| \|	The flow allocator now passes the full qos specification to the endpoint, instead of just a cube. This is a more flexible architecture, as it makes QoS cubes internal to the layers. Adds endianness transforms for the flow allocator protocol in the normal IPCP. Signed-off-by: Dimitri Staessens <dimitri.staessens@ugent.be> Signed-off-by: Sander Vrijders <sander.vrijders@ugent.be>
*	lib: Add a data qos cube	Dimitri Staessens	2018-06-08	1	-8/+19
\| \| \| \| \| \| \| \|	This adds a data qos cube that is reliable. Reliable qos can be selected by setting the loss parameter of the qosspec to 0. Signed-off-by: Dimitri Staessens <dimitri.staessens@ugent.be> Signed-off-by: Sander Vrijders <sander.vrijders@ugent.be>
*	lib: Define default qosspecs in qos sources	Dimitri Staessens	2018-06-05	1	-0/+32
\| \| \| \| \| \| \| \| \|	This moves the definition of the predefined qosspecs to qos.h and qos.c. This allows applications to select them using qos_best_effort etc. Signed-off-by: Dimitri Staessens <dimitri.staessens@ugent.be> Signed-off-by: Sander Vrijders <sander.vrijders@ugent.be>
*	include, src: Update copyright to 2018	Dimitri Staessens	2018-01-09	1	-1/+1
\| \| \| \| \| \| \|	Happy New Year, Ouroboros. Signed-off-by: Dimitri Staessens <dimitri.staessens@ugent.be> Signed-off-by: Sander Vrijders <sander.vrijders@ugent.be>
*	lib: Add fccntl configuration command	dimitri staessens	2017-08-31	1	-6/+0
\| \| \| \| \| \| \|	This replaces the flow_set_* commands with a single fccntl command that can configure flows and the FRCT instance. For more details, see "man 3 fccntl".
*	build: Replace fsf snail mail with contact URL	dimitri staessens	2017-08-13	1	-2/+1
\|
*	lib, ipcpd, irmd: Add full-fledged QoS	Sander Vrijders	2017-06-21	1	-0/+57
	This adds more Quality of Service support to Ouroboros. One part is the network specific characteristics such as bandwidth, delay, ... The other part is end-to-end QoS like reliability, window based flow control, ...