20/10/2020 17:02, Stephen Hemminger:
> Thomas Monjalon wrote:
> > 05/09/2020 00:31, Stephen Hemminger:
> > > If using lots of queues and ports, and having per port or per queue
> > > metrics it is easy to exceed the upper bound of the metric library.
> > > Move the limit into rte_config where user
On Tue, 20 Oct 2020 13:50:55 +0200
Thomas Monjalon wrote:
> 05/09/2020 00:31, Stephen Hemminger:
> > If using lots of queues and ports, and having per port or per queue
> > metrics it is easy to exceed the upper bound of the metric library.
> > Move the limit into rte_config where user can change
05/09/2020 00:31, Stephen Hemminger:
> If using lots of queues and ports, and having per port or per queue
> metrics it is easy to exceed the upper bound of the metric library.
> Move the limit into rte_config where user can change it.
>
> Ideally, there would be no upper bound and a dynamic struc
On Fri, 4 Sep 2020 15:31:19 -0700
Stephen Hemminger wrote:
> If using lots of queues and ports, and having per port or per queue
> metrics it is easy to exceed the upper bound of the metric library.
> Move the limit into rte_config where user can change it.
>
> Ideally, there would be no upper
If using lots of queues and ports, and having per port or per queue
metrics it is easy to exceed the upper bound of the metric library.
Move the limit into rte_config where user can change it.
Ideally, there would be no upper bound and a dynamic structure
such as red-black tree or hash table would
5 matches
Mail list logo
