Adaptive Quality of Service Architecture 1.0.0-rc2 (qosres branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Adaptive Quality of Service Architecture 1.0.0-rc2 (qosres branch)
# 1  
Old 01-12-2008
Adaptive Quality of Service Architecture 1.0.0-rc2 (qosres branch)

Image AQuoSA is an open architecture for the provisioning of adaptive Quality of Service functionality into the Linux kernel. The project features a flexible, portable, and lightweight software architecture for supporting QoS-related services on top of a general-purpose operating system as Linux. The architecture is well founded on formal scheduling analysis and control theoretical results. At the core of the software is an adaptive Resource Reservation layer that is capable of dynamically adapting the CPU allocation for QoS-aware applications based on their run-time requirements. License: GNU Lesser General Public License (LGPL) Changes:
A few configuration-related bugs have been fixed.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Adaptive Information Technology for Service Lifecycle Management

HPL-2008-80 Adaptive Information Technology for Service Lifecycle Management - Rolia, Jerry; Belrose, Guillaume; Brand, Klaus; Edwards, Nigel; Gmach, Daniel; Graupner, Sven; Kirschnick, Johannes; Stephenson, Bryan; Vickers, Paul; Wilcock, Lawrence Keyword(s): Software as a Service, Enterprise... (0 Replies)
Discussion started by: Linux Bot
0 Replies
Login or Register to Ask a Question
scmp_sys_resolver(1)					     libseccomp Documentation					      scmp_sys_resolver(1)

NAME
scmp_sys_resolver - Resolve system calls SYNOPSIS
scmp_sys_resolver [-h] [-a ARCH ] [-t] SYSCALL_NAME | SYSCALL_NUMBER DESCRIPTION
This command resolves both system call names and numbers with respect to the given architecture supplied in the optional ARCH argument. If the architecture is not supplied on the command line then the native architecture is used. If the "-t" argument is specified along with a system call name, then the system call will be translated as necessary for the given architecture. The "-t" argument has no effect if a system call number is specified. In some combinations of architecture and system call, a negative system call number will be displayed. A negative system call number indi- cates that the system call is not defined for the given architecture and is treated in a special manner by libseccomp depending on the operation. -a ARCH The architecture to use for resolving the system call. Valid ARCH values are "x86", "x86_64", "x32", and "arm". -t If neccessary, translate the system call name to the proper system call number, even if the system call name is different, e.g. socket(2) on x86. -h A simple one-line usage display. EXIT STATUS
Returns zero on success, errno values on failure. NOTES
The libseccomp project site, with more information and the source code repository, can be found at http://libseccomp.sf.net. This tool, as well as the libseccomp library, is currently under development, please report any bugs at the project site or directly to the author. AUTHOR
Paul Moore <paul@paul-moore.com> paul@paul-moore.com 23 May 2013 scmp_sys_resolver(1)