Recent Commits to NES-Open-Switch:master

Showing posts with label remapping. Show all posts
Showing posts with label remapping. Show all posts

Tuesday, April 21, 2015

Bridge CoS update - 10

Added changes in ethernet module for traversing #port #level #access #priority #remapping configuration. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 82 ...
[commit ef219b5ee6c0ebdb066c920e1b11fc02a5197154]

Monday, April 20, 2015

Bridge CoS update - 9

Added changes in ethernet module for traversing #port #level #CoS #remapping configuration. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 81 ...
[commit 59c6924795664ff8cdda4a2b4c0cec202a1ce2a7]

Friday, April 10, 2015

Bridge CoS update - 6

Added changes in ethernet module for traversing #port #level #service #access #priority #remapping configuration entries on provider bridges. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 74 ...
[commit da62efad1123bdbf472ceff31c9529ff49d28250]

Tuesday, March 31, 2015

Bridge CoS update - 4

Added optimizations for #port #level #service #access #priority #remapping configuration on provider bridges. This will reduce the memory requirement for supporting service access priority remapping configuration. The service access priority remapping will enable to map #customer #CoS on frames to a different CoS value at the provider network border - either on a customer edge port ( #CEP ) or a customer network port ( #CNP ) -, while receiving data from the customer network. This is useful to request priority handling of customer frames in the provider network. The remapped CoS will be used int the provider network for effective #QoS treatment on the frame. By default, for a frame the ingress CoS is used unaltered.

#Ethernet update 68 ...
[commit 416f683112105b43bdca799b83e8ed23f748a54e]

Monday, March 30, 2015

Bridge CoS update - 3

Added optimizations for #port #level #access #priority #remapping configuration on customer bridges. This will reduce the memory requirement for supporting access priority remapping configuration. The access priority remapping will enable to map #customer #CoS on frames to a different CoS value at the customer domain border, while sending data to the provider network. This is useful when the #SLA with the #provider #network requires specific kind of CoS mapping for required QoS treatment. The remapped CoS will be used int the provider network for effective #QoS treatment on the frame. By default, for a frame the egress CoS is send unaltered.

#Ethernet update 67 ...
[commit 927d1b2c75c52888f6a251138ed93a9e58c914a6]

Thursday, March 19, 2015

Bridge CoS update

Added corrections for #general #bridge #port #CoS #configuration in ethernet module. The general configuration controls the default CoS applied on frames, number of traffic classes supported, PCP row to be used for remarking of frames, etc ...

Added optimizations for #port #level #CoS #remapping configuration. This will reduce the memory requirement for supporting CoS remapping configuration. The CoS remapping will enable to map CoS on frames to a different CoS value. The remapped CoS will be used for effective #QoS treatment on the frame. By default, for a frame the ingress CoS is considered as the #effective #CoS for QoS handling.

#Ethernet update 61 ...
[commit 45523fe6405229f8f91f0bd77771646acbb9ce85]