Hi, I have some questions about the QoS NSLP implementation.
1. The current QoSServer can have only one QoSFSM at one time, but can this deal with multiple QoS-NSLP sessions which starting from different QNIs? If it's possible, how can the only FSM in QoSServer deal with the sessions associated with it's states?
2. As I know, the flows managed by NSIS protocol should be associated with linux traffic control (tc). How can I map the QSPEC managed by QoS NSLP into the Linux tc (cbq)?
Hi,
Hi, I have some questions about the QoS NSLP implementation.
Just out of curiosity: Did the previous mail help you?
- The current QoSServer can have only one QoSFSM at one time, but can
this deal with multiple QoS-NSLP sessions which starting from different QNIs? If it's possible, how can the only FSM in QoSServer deal with the sessions associated with it's states?
That is not exactly true. You are right, the QoSServer class has a member named fsm (QoSServer::fsm), but this variable is set on every incoming request to the corresponding fsm. Therefore, the QoSServer supports multiple sessions.
For example: Look at QoSServer::handleRecvMessage(). There you find: fsm=get_fsm_for_sid(s->sid); This line looks in a table for the FSM associated with the specified Session ID and writes it to the fsm member variable.
- As I know, the flows managed by NSIS protocol should be associated with
linux traffic control (tc). How can I map the QSPEC managed by QoS NSLP into the Linux tc (cbq)?
Please have a look at the beta page of our new website: http://user.informatik.uni-goettingen.de/~nsis/beta.html
There you will find a recent development version 0.4.1-dev. It has initial support for the RMF (Ressource Management Function). Normally, the NullRMF is used, which does nothing. You can activate the SimpleRMF, by changing lines 67 and 68 of QoSServer.cpp. The SimpleRMF uses Traffic Control (tc) with the Hierachical Token Bucket (HTB). Currently, most parameters are hardcoded. For example SimpleRMF.cpp says that overall bandwidth is always 100 Mbit/s and every reservation gets 100 kbit/s rate and 150 kbit/s peak rate.
The RMF does not support tearing down reservations yet, nor does it support any QSpec or any kind of configuration.
I hope this helps.
Regards, Christian Dickmann
nsis_imp@informatik.uni-goettingen.de