Hi Bala,
OK, thanks for your clarification. I will add the user limit in the example
instead of TM library.
Thanks,
Forrest
On 4 November 2016 at 11:26, Bala Manoharan
wrote:
> The statistics of "total" packets one user can enqueue can be easily
> calculated by the application meaning there is
The statistics of "total" packets one user can enqueue can be easily
calculated by the application meaning there is no need of any
implementation support. This can be simply calculated over a counter
in the application which increments when packets are transmitted for a
single user.
The Threshold
Hi Bala,
This is what the current TM does.
The max_packets is "active" packets in the TM queue, but not the "total"
packets of one user can enqueue.
"max active packets" in a TM queue is implementation things and the user
may not care about it.
What the use cares is how many bytes(max_bytes/pack
The threshold parameters are added to the tm queue mainly for tail
drop and WRED supported by some TM systems. It denotes the number of
active packets that can enqueued in the queue at any given instant If
threshold is required per user then the application can create a
single TM queue per user and
This question properly belongs on the ODP mailing list (+cc)
On Wed, Nov 2, 2016 at 4:12 AM, Forrest Shi wrote:
> Hi,
>
> I can see some COS profile param like below in the example:
>
> .threshold_params = {
> .max_pkts = 1,.enable_max_pkts = TRUE,
> .m
